The SeaMonkey core developers have ACKed the plan to bump the version numbers on the "new release process" repos to the new scheme as follows: We're bumping suite/config/version.txt on comm-central to "2.4a1", on comm-aurora to "2.3a2" and on comm-beta to "2.2". As noted in bug 662277, I need to bump version-50.txt on comm-beta in addition to that, as it's using the Mozilla 5 platform. This bug is just here to have something to refer to in the checkin comments. ;-)
http://hg.mozilla.org/comm-central/rev/2ce1037fbf74 http://hg.mozilla.org/releases/comm-aurora/rev/ba7244526210 http://hg.mozilla.org/releases/comm-beta/rev/5fde5647d1dc
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
FWIW, I have seen comm-aurora tinderbox-builds named seamonkey-2.3a2.en-US.* but all comm-central tinderbox-builds are still calling themselves 2.2a1pre, as follows, with file timestamps in PDT, from the HTTP access to ftp.mozilla.org - "dm-ftp01.mozilla.org in the Pacific Time Zone (PST/PDT)": 06-Jun-2011 17:21 seamonkey-2.2a1pre.en-US.win32.installer.exe 06-Jun-2011 17:21 seamonkey-2.2a1pre.en-US.win32.zip 06-Jun-2011 11:52 seamonkey-2.2a1pre.en-US.linux-i686.tar.bz2 06-Jun-2011 16:31 seamonkey-2.2a1pre.en-US.linux-x86_64.tar.bz2 06-Jun-2011 16:15 seamonkey-2.2a1pre.en-US.mac.dmg
I think its b/c its dep builds, but not sure. Either way tonights nightlies *should* change.
(In reply to comment #3) > I think its b/c its dep builds, but not sure. Either way tonights nightlies > *should* change. comm-central: Mozilla/5.0 (X11; Linux x86_64; rv:7.0a1) Gecko/20110607 Firefox/7.0a1 SeaMonkey/2.4a1 ID:20110607003003 and, at http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk/ seamonkey-2.4a1.en-US.linux-x86_64.tar.bz2 07-Jun-2011 06:29 23M seamonkey-2.4a1.en-US.mac.dmg 07-Jun-2011 08:29 41M seamonkey-2.4a1.en-US.linux-i686.tar.bz2 07-Jun-2011 09:43 21M seamonkey-2.4a1.en-US.win32.installer.exe 07-Jun-2011 12:24 15M seamonkey-2.4a1.en-US.win32.zip 07-Jun-2011 12:24 19M seamonkey-2.4a1.en-US.langpack.xpi 07-Jun-2011 12:24 824K comm-aurora: no nightlies AFAICT 06-Jun-2011 22:40 http://ftp.mozilla.org/pub/mozilla.org/seamonkey/tinderbox-builds/comm-aurora-linux64/1307413821/seamonkey-2.2a1pre.en-US.linux-x86_64.tar.bz2 06-Jun-2011 22:42 http://ftp.mozilla.org/pub/mozilla.org/seamonkey/tinderbox-builds/comm-aurora-macosx64/1307413821/seamonkey-2.2a1pre.en-US.mac.dmg the above two, too early? 07-Jun-2011 02:09 http://ftp.mozilla.org/pub/mozilla.org/seamonkey/tinderbox-builds/comm-aurora-linux/1307413821/seamonkey-2.3a2.en-US.linux-i686.tar.bz2 07-Jun-2011 04:47 http://ftp.mozilla.org/pub/mozilla.org/seamonkey/tinderbox-builds/comm-aurora-win32/1307413821/seamonkey-2.3a2.en-US.win32.installer.exe comm-beta: no nightlies AFAICT 07-Jun-2011 03:48 http://ftp.mozilla.org/pub/mozilla.org/seamonkey/tinderbox-builds/comm-beta-win32/1307426133/seamonkey-2.2.en-US.win32.installer.exe 07-Jun-2011 07:23 http://ftp.mozilla.org/pub/mozilla.org/seamonkey/tinderbox-builds/comm-beta-linux/1307426133/seamonkey-2.2.en-US.linux-i686.tar.bz2 07-Jun-2011 12:17 http://ftp.mozilla.org/pub/mozilla.org/seamonkey/tinderbox-builds/comm-beta-linux64/1307468585/seamonkey-2.2a1pre.en-US.linux-x86_64.tar.bz2 07-Jun-2011 12:32 http://ftp.mozilla.org/pub/mozilla.org/seamonkey/tinderbox-builds/comm-beta-macosx64/1307468585/seamonkey-2.2.en-US.mac.dmg Didn't check: debug and localized builds, mar files, files other than installable archives and langpacks I'm setting this VERIFIED on the assumption that the *next* comm-aurora tinderbox-builds for linux64 and macosx64 will be called 2.3a2 like the others. Don't REOPEN unless they do. If some other build, later than the ones listed above, goes back to an earlier version number (not likely, but who knows), I think it'd be better to open a new bug with the "regression" keyword.
Status: RESOLVED → VERIFIED
oh-oh, the comm-beta linux64 will also have to be watched. Not reopening -yet- for an "unofficial" branch.
The ones still reporting as 2.1a1pre might just need a clobber, but for tinderbox-builds it doesn't matter too much, and daily builds (once they get turned on for aurora) or beta builds (that go through the release machinery) will not have that problem as they're always clobbers.
You need to log in before you can comment on or make changes to this bug.