644433 - Bump SeaMonkey version on trunk for post-2.1 development

Status: RESOLVED FIXED

(SeaMonkey :: Build Config, defect)

Description

[Robert Kaiser]

We'll need to bump the SeaMonkey version on trunk to note that the version with mozilla-central is not what's coming in 2.1, which will use mozilla-2.0 instead.

Note that along with that, we'll need to teach AUS that this new version series refers to trunk.

Also, we'll need to add this version to AMO (I have admin privs there and can do it) so add-ons can refer to it.

Comment 1

[Justin Wood (:Callek)]

(In reply to comment #0)
> We'll need to bump the SeaMonkey version on trunk to note that the version with
> mozilla-central is not what's coming in 2.1, which will use mozilla-2.0
> instead.

Easy, KaiRo if you want to land this rs+=me for 2.2a1pre

> Note that along with that, we'll need to teach AUS that this new version series
> refers to trunk.

In practice, this means what? (Have a bug # for ref or anything)

> Also, we'll need to add this version to AMO (I have admin privs there and can
> do it) so add-ons can refer to it.

We don't _necessarily_ need to add it yet, which can cause addon author confusion; but I think we should anyway, yea.

Comment 2

[Robert Kaiser]

(In reply to comment #1)
> (In reply to comment #0)
> > We'll need to bump the SeaMonkey version on trunk to note that the version with
> > mozilla-central is not what's coming in 2.1, which will use mozilla-2.0
> > instead.
> 
> Easy, KaiRo if you want to land this rs+=me for 2.2a1pre

Not without coordination of those other items!

> > Note that along with that, we'll need to teach AUS that this new version series
> > refers to trunk.
> 
> In practice, this means what? (Have a bug # for ref or anything)

Something similar to attachment 521336 [details] [diff] [review], but we have ours only locally on aus2-community (in /opt/aus2 there is an application directory, the app is just some PHP and the config is included from the inc/ subdir).

> > Also, we'll need to add this version to AMO (I have admin privs there and can
> > do it) so add-ons can refer to it.
> 
> We don't _necessarily_ need to add it yet, which can cause addon author
> confusion; but I think we should anyway, yea.

Oh, but we do, as else no add-on at all can work with the nightlies (and I would e.g. like to make the German dictionaries work)!

Comment 3

[Robert Kaiser]

[root@cb-ausstage01 ~]# cd /opt/aus2/app/inc/
[root@cb-ausstage01 inc]# ls -l /opt/aus2/incoming/2/SeaMonkey/
total 20
drwxr-xr-x  6 seabld seamonkey 4096 May 23  2009 comm-1.9.1
drwxr-xr-x  6 seabld seamonkey 4096 Mar 16 08:58 comm-2.0
drwxr-xr-x  7 seabld seamonkey 4096 Jul 12  2009 comm-central-trunk
drwxr-xr-x  5 seabld seamonkey 4096 Jul 13  2008 hg-test
drwxr-xr-x  5 seabld seamonkey 4096 Jan 16  2008 trunk
[root@cb-ausstage01 inc]# nano config.php

In line 131ff. changed the block from

    'SeaMonkey'   =>  array(
        '2.0*'    =>  'comm-1.9.1',
        '2.1*'    =>  'comm-central-trunk'
    ),

to

    'SeaMonkey'   =>  array(
        '2.0*'    =>  'comm-1.9.1',
//        '2.1*'    =>  'comm-2.0'
        '2.1*'    =>  'comm-central-trunk'
        '2.2*'    =>  'comm-central-trunk'
    ),

The commented-out line will need to be activated and the one below it removed once we don't want the people currently on a "2.1*" nightly to go to a trunk but instead a "comm-2.0" nightly.

Comment 4

[Robert Kaiser]

Callek says we're bumping the version right now and we want current "2.1" nightly users to go "comm-2.0", i.e. stay on 2.1 (if they want to go to 2.2a1pre, they need to download a fresh nightly and then will stay on that one), so doing the other change as well, ending up with:

    'SeaMonkey'   =>  array(
        '2.0*'    =>  'comm-1.9.1',
        '2.1*'    =>  'comm-2.0'
        '2.2*'    =>  'comm-central-trunk'
    ),

Comment 5

[Robert Kaiser]

And 2.2a1pre added to AMO, so we're ready to go (note that we might need checkins to all shipped add-ons to make them support that new maxVersion).

Comment 6

[Justin Wood (:Callek)]

http://hg.mozilla.org/comm-central/rev/81fff64b237e

(In reply to comment #5)
> And 2.2a1pre added to AMO, so we're ready to go (note that we might need
> checkins to all shipped add-ons to make them support that new maxVersion).

Thanks for the reminder, pushed ver bumps to cz, inspector, and venkman repo's.
debugQA, and our two themes derive that from the build system.

Comment 7

[[e-mail]]

(In reply to comment #5)
> And 2.2a1pre added to AMO, so we're ready to go (note that we might need
> checkins to all shipped add-ons to make them support that new maxVersion).
That won't help people updating an existing profile, of course. They'll need cz/inspector/venkman/debugqa marked as compatible with 2.2a1pre on AMO.

Comment 8

[Robert Kaiser]

(In reply to comment #7)
> (In reply to comment #5)
> > And 2.2a1pre added to AMO, so we're ready to go (note that we might need
> > checkins to all shipped add-ons to make them support that new maxVersion).
> That won't help people updating an existing profile, of course. They'll need
> cz/inspector/venkman/debugqa marked as compatible with 2.2a1pre on AMO.

Right, that's one of the reasons why I noted we need to add this version in AMO, which I did.

Comment 9

[Serge Gautherie (:sgautherie)]

http://hg.mozilla.org/venkman/rev/10ee9dce95c6
"bump SeaMonkey's version number"
+
http://hg.mozilla.org/venkman/rev/14cac28a508c
"Venkman locales too"

Comment 10

[Serge Gautherie (:sgautherie)]

http://hg.mozilla.org/dom-inspector/rev/a91d79f80f95
"bump SeaMonkey's version number"
http://hg.mozilla.org/dom-inspector/rev/0bb7db177214
"Merge"