reminder ticket to discuss this, see http://codereview.musicbrainz.org/r/1361/
Decided by http://scheduling.ocharles.org.uk/results and http://chatlogs.musicbrainz.org/musicbrainz-devel/2011/2011-12/2011-12-05.html
Added schema change component.
I'm already assigned, so here's what this should look like: there are four things that matter for a timeline event: date, title, description, link. I propose a new table should be added for timeline events, with date as a primary key (it doesn't work with the graph if there's more than one per date anyway), unless the other devs want a surrogate key of some sort.
Once the table exists, the timeline-graph code can be migrated to use it, and the existing events put into the table.
This ticket is under consideration for the May 15h schema change release. Please do the following:
This looks good, but does it belong in the MusicBrainz schema? Maybe we should introduce a statistics schema?
I don't care one way or the other; I'll leave that decision to you folks who care about the schema more. If a new schema is introduced, I'd recommend moving the 'statistic' table as well (but I'm sure you knew that).
I'd rather not introduce a new schema, because it complicates tables export/import and live data feed (the 'statistic' table is a replicated table, as should probably be the new 'timeline_event' table).
Rob's comment said this is under consideration for the May 5th schema change, but it was in the wrong fix version. As there are no other comments, I'm moving it to the May 5th fix version.
In review at http://codereview.musicbrainz.org/r/1876/diff/#index_header