1084144 - (SM2.31b1) Tracking bug for build and release of SeaMonkey 2.31 Beta 1

Status: RESOLVED FIXED

(SeaMonkey :: Release Engineering, defect, P1)

Description

[Edmund Wong (:ewong)]

This is a tracking bug for Build and Release of SeaMonkey 2.31 Beta 1

We expect an actual release on Wednesday 22nd October.  However if things
are smooth, we will release on Monday 20th October.

Comment 1

[Edmund Wong (:ewong)]

Attachment: Update configs for SeaMonkey 2.31b1

Comment 2

[Edmund Wong (:ewong)]

Comment on attachment 8508377 [details] [diff] [review]
Update configs for SeaMonkey 2.31b1

Pushed to buildbot-configs:
https://hg.mozilla.org/build/buildbot-configs/rev/6a865908c89a

Comment 3

[Edmund Wong (:ewong)]

Please note that due to repack issues and a slight master weirdness,
2.31b1 is delayed until at least tomorrow (24th October PST).

Comment 4

[Edmund Wong (:ewong)]

Due to the OSX signing changes, we've encountered a problem with the
patcher updates.  As such, 2.31b1 is going to be delayed till Monday at the
earliest.

Comment 5

[Grinch]

just tested the build 1 SM 2.31 b1 (german). Got some problems showing flash video. At one time only sound but with a video as expected. Otherwise nothing happend by pushing the start stream button. SM 2.30 does it.

Comment 6

[Grinch]

same problem with trying to watch a stream in html5. only sound but no Vid.

Comment 7

[Edmund Wong (:ewong)]

(In reply to Edmund Wong (:ewong) from comment #4)
> Due to the OSX signing changes, we've encountered a problem with the
> patcher updates.  As such, 2.31b1 is going to be delayed till Monday at the
> earliest.

An update: 2.31b1 is blocked on the osx signing changes between 2.30b2 and
2.31b1.  The patchers on the m-b side are geared towards the v2 changes (i.e. 
expecting 2.30b2 to be v2 signed) but our 2.30b2 is v1 so the update patching
is failing.

I'm wondering if we can just copy the old make_incremental_update.py to the
tools' repo and check if the application.ini is in the Resources/ dir. If so,
it uses the new m-b make_incremental_update.py; otherwise, use the old one.
Though the problem is, the old one won't recognize the v2 changes.

So we introduce a 'mixed mode' make_incremental_update.py script?

Comment 8

[Edmund Wong (:ewong)]

Ok...  everything seemed to be unblocked now (so far... osx64 updates verification passed.  so now I'm proceeding until mirrorpush. 

This means that both the bouncer and web site can be done now. (barring any
other unforeseen blockages...)

Comment 9

[Jens Hatlak (:InvisibleSmiley)]

This one is done, no? One needinfo pending from comment 7, though.

Comment 10

[Edmund Wong (:ewong)]

This is fixed.