Philip Chee wrote:
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.
Sounds like I should just run the last 2.0.1pre and be happy. It works, I use it
on almost all my machines (unless forms are needed or I have multiple profiles),
and I was looking for something which worked not new features.
Thanks for the clarification.
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)
It's all the same code as SeaMonkey, though, just in a different package. Be
glad they didn't pick something like mersine primes for version numbers.
--
Bill Davidsen <david...@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
