[cosmo-dev] 0.9 post mortem
Bobby Rullo
br at osafoundation.org
Thu Nov 15 14:54:40 PST 2007
Here's some thoughts I've had after the 0.9.0 Revert/Data Loss Fiasco
of 07
1) We should have DB Revert scripts. This doesn't mean a script which
reverts to the backup. What I am talking about is a script which
i) Makes a post-update backup of the database
ii) Migrates the database backwards to the old (previous release)
schema
Obviously this is only for releases which have a schema change. I'm
not saying that we have to have this for every database we support -
just for hub. Maybe it's not even the Cosmo team's job, maybe it's Hub
(working with Cosmo team of course)
2) I don't think we should have any release dependent on roving
"SNAPSHOT" - it makes bugs difficult to reproduce, since you
potentially get a different build every day. When we test an RC, we
should pin to that day's SNAPSHOT.
3) I'm not sure to what extent we are doing this, but we need to make
sure to test on a cosmo instance with migrated data. This testing may
or may not include the normal windmill stuff, but it should have added
performance stuff, so we know if things are way out of wack.
bobby
More information about the cosmo-dev
mailing list