upgrading b.m.o; developer's release

Joel Peshkin bugreport at peshkin.net
Wed Oct 30 14:49:57 UTC 2002

Myk Melez wrote:

> <snip>
> How about generating a short list of things we want in for the 
> developer's release and then freezing the trunk to all except those 
> fixes for about a week before the upgrade (i.e. by Friday, November 
> 1)? Ideally we'd have everything in before that date so we have a week 
> to test the trunk before it goes into production on b.m.o.
> Also ideally we'd release the developer's release a few days before 
> b.m.o upgrades so other installations have a chance to shake out some 
> of the regressions first.
> <snip>


     So you are pulling the release that goes to BMO sometime between 
Nov 1 and Nov 8, correct?   Why not pull a controlled branch just like 
any other stable release on Nov 1 and have any changes to the tip 
applied to both ONLY if needed for BMO?


More information about the developers mailing list