On Sun, Nov 29, 2009 at 11:06 AM, Sune Foldager <sune.folda...@me.com> wrote: > Steve Borho wrote: >> Once 0.9.1 is released, the stable branch will be locked down in "bug >> and documentation fixes only" mode, as is customary. > > Hmm, isn't that more customary to do *before* a release, to increase the > likelyhood of actually stable code..?
This is customary for TortoiseHg. If we had an actual Q/A team, or more than a handful of people testing the release candidates, we wouldn't have a need to need to do this. We don't get a lot of feedback on new features until the .0 release. So we reserve the right to tweak things a bit in the .1 and then lock everything down for the remaining point releases. In practice, .0 ends up being a release candidate for .1. But if we called it that no-one would use it and we'd end up with the same problem. Mercurial has the same problem with their point releases. Hardly anyone tries the tip code before the release, so quick .1 releases have been common. -- Steve Borho ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tortoisehg-develop mailing list Tortoisehg-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
