Opened 9 years ago

Closed 9 years ago

#2912 closed task (wontfix)

Tag and release metrics-db version 0.0.1

Reported by: karsten Owned by: karsten
Priority: Medium Milestone:
Component: Metrics/CollecTor Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


We should start tagging metrics-db versions and write a ChangeLog.

In theory, there won't be many metrics-db instances, because we already provide all the metrics data that researchers and interested users need. But who knows. We shouldn't have to worry about breaking people's stuff when changing metrics-db, so let's give them stable versions.

Before we can tag we should clean up the documentation a bit. Probably.

Child Tickets

Change History (2)

comment:1 Changed 9 years ago by karsten

Here are a couple of sub tasks copied from my local notes:

  • Try setting up a new metrics-db on a fresh Squeeze EC2 instance and confirm that doc/manual.tex contains all the required steps.
  • Remove the irrelevant parts and possibly move them to metrics-web's doc/manual.tex (see #2913).
  • Add generic versions of the relevant shell scripts from yatei to a new bin/ directory.
  • Add a README.

comment:2 Changed 9 years ago by karsten

Resolution: wontfix
Status: newclosed

I'm not convinced anymore that we need metrics-db releases. We should focus on making the output data available in a more convenient way and give up on the idea that anyone else would want to run their own metrics-db instance.

Now, we could change this ticket to "Clean up the metrics-db documentation," but we could open similar tickets for pretty much every component. And refactor the code. And add unit tests. But that needs a more general approach than having a single ticket for cleaning up the metrics-db documentation. No ticket required to remember that.


Note: See TracTickets for help on using tickets.