----- Original Message ----- > From: "Eoghan Glynn" <egl...@redhat.com> > To: "Dan Prince" <dpri...@redhat.com> > Cc: openstack@lists.launchpad.net > Sent: Friday, April 27, 2012 5:45:27 AM > Subject: Re: [Openstack] database migration cleanup > > > > > https://review.openstack.org/#/c/6847/ > > Nice! > > > * Migrations added during Folsom release cycle could be compacted > > during "E" release cycle. TBD if/when we do the next compaction. > > An alternative idea would be to do the compaction *prior* to the > Folsom relase instead of after, so that the cleanest possible > migration path is presented to non-trunk-chasing users. It could for > example be a task that's part of spinning up the first Folsom-RC. > > Its unlikely that after new migrations are added after the release > candidate goes out the door (as these are generally associated with > non-trivial new features, which would have missed the boat at that > late stage). But if there are any, these would have to be adde to > the squashed aggregate migration from the get-go.
I thought about this... but that still leaves only a couple weeks to catch any issues that might come up in the release candidate phase. Also, using the RC makes the compaction point a bit more fuzzy for end users who are following trunk more closely. I do like that it would keep the release tree cleaner however. Performing the compaction after release is sort of a middle ground approach which should allow us to clean house from time to time but also keep things stable around release time. > > Cheers, > Eoghan > > _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
