On Sun, 06 Dec 2009 21:56:34 -0500, Bill Davidsen wrote: > I have been running 2.0.1pre for a while to get the fix for NNTP posting > badness. Now I'm told there's a security upgrade to 2.0.2pre. Is there any > intention of releasing 2.01 before adding a bunch of new untested changes and > calling it 2.0.2? Or should I just stop at the working version I have and be > happy?
Due to the way the release automation scripts work. Whenever a release branch (e.g. 2.0.1) is cut, the tip of the branch is automatically bumped to the smallest next increment e.g. 2.0.2pre. If you are on the nightly branch channel you'll get updated to the latest tip rather to any of the "relbranch" side branches. Similarly if/when a new major branch is cut from the trunk (e.g. 2.1) the tip of the trunk will be bumped to e.g. 2.2a1pre (unless you are firefox where you get silly progressions like 2.0 -> 2.5 -> 3.0 -> 3.5 -> 3.6 -> 3.7 -> 4.0) Phil -- Philip Chee <[email protected]>, <[email protected]> http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. [ ]I wish I could remember where I parked my hard disk.... * TagZilla 0.066.6 _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
