Bug 1459133 (SM2.49.4)

Tracking bug for build and release of SeaMonkey 2.49.4

RESOLVED FIXED in seamonkey2.49

Status

enhancement
P1
blocker
RESOLVED FIXED
Last year
7 months ago

People

(Reporter: ewong, Assigned: ewong)

Tracking

(Blocks 1 bug)

SeaMonkey 2.49 Branch
seamonkey2.49
Dependency tree / graph

SeaMonkey Tracking Flags

(seamonkey2.49esr fixed)

Details

()

Attachments

(4 attachments, 2 obsolete attachments)

Assignee

Description

Last year
This is a tracking bug for Build and Release of SeaMonkey 2.49.4

We expect an actual release on tba.
Assignee

Updated

Last year
Depends on: 1459134
Depends on: 1298487
Version: SeaMonkey 2.52 Branch → SeaMonkey 2.49 Branch
Depends on: 1428104
The TB branch has been updated for TB 52.8. I have not seen any new regressions pop up or reported so in theory we could start building. Lets discuss this Sunday.
Accidently pushed to the old 2.49.3 release branch first 
https://hg.mozilla.org/releases/comm-esr52/rev/d3380b0a4ffd5b1fa556f1b42451359148485131

https://hg.mozilla.org/releases/comm-esr52/rev/186f453358f0eec029a854d4a62698b4c73ba0dc

The final csets for 2.49.4 are:


comm-esr52 SEAMONKEY_2_49_ESR_RELBRANCH
186f453358f0 merge rev b6dbcbdec116 to SEAMONKEY_2_49_ESR_RELBRANCH 

mozilla-esr52 THUNDERBIRD_52_VERBRANCH
babe11f6b2bc merge default to THUNDERBIRD_52_VERBRANCH. a=jorgk DONTBUILD
We should probably wait with building till this is fixed:

https://blog.mozilla.org/thunderbird/2018/05/efail-and-thunderbird/

Ben, is there a bug for Thunderbird/mailnews for it? Could you add me to cc then.
Flags: needinfo?(ben.bucksch)
Found them
Depends on: 1462481, 1462488
Flags: needinfo?(ben.bucksch)
Assignee

Updated

Last year
Depends on: 1463953
Assignee

Comment 5

Last year
(assuming no change in l10n csets)
Assignee: nobody → ewong
Status: NEW → ASSIGNED
Attachment #8982085 - Flags: review?(frgrahl)
Comment on attachment 8982085 [details] [diff] [review]
[configs] Update configs for SeaMonkey 2.49.4 (build 1)

Looks good
Attachment #8982085 - Flags: review?(frgrahl) → review+
Depends on: 1468079
Depends on: 1468492
The really (until we change our mind again) final csets for 2.49.4 are:

comm-esr52 SEAMONKEY_2_49_ESR_RELBRANCH
cbdc217e6466 merge default to SEAMONKEY_2_49_ESR_RELBRANCH. a=frg DONTBUILD

https://hg.mozilla.org/releases/comm-esr52/rev/cbdc217e6466b34e9695d901901291ef55be856b

mozilla-esr52 THUNDERBIRD_52_VERBRANCH
6d47f732232d merge default to THUNDERBIRD_52_VERBRANCH. a=jorgk DONTBUILD
Assignee

Updated

Last year
Attachment #8989289 - Flags: review?(ewong) → review+
2.49.4 is now happily building so updated the default branch with the next version:

https://hg.mozilla.org/releases/comm-esr52/rev/eb5d99108c1a5080566a459722ceccc2dac629e5

ewong, I see no movement in the bouncer bug. Maybe you want to inquire.
ewong we need to stop building 2.49.4. TB 52.9 has a nasty bug which needs to be fixed first:
bug 1473893
Depends on: 1473893
Flags: needinfo?(ewong)
ewong I pushed the attachment fix to the SEAMONKEY_2_49_ESR_RELBRANCH:

https://hg.mozilla.org/releases/comm-esr52/rev/8a9f075930d365046f391ed2008ba28cf850bdbb

The new cset for comm-esr52 is 8a9f075930d3. See the picture for the current head structure. You better look into the configs yourself.
Assignee

Comment 12

Last year
Flags: needinfo?(ewong)
Attachment #8990875 - Flags: review?(frgrahl)
Comment on attachment 8990875 [details] [diff] [review]
[configs] Update for SeaMonkey 2.49.4 (build 1) [w/ sec fix cset]

r+ but you put a trailing space after the 1 in. Check the patch. And comment says build 2.
Attachment #8990875 - Flags: review?(frgrahl) → review+
Comment on attachment 8990877 [details] [diff] [review]
[configs] Update for SeaMonkey 2.49.4 (build 1) [w/ sec fix cset] (v2)

A+++
Attachment #8990877 - Flags: review?(frgrahl) → review+
Assignee

Updated

Last year
Depends on: 1474491
2.49.4 was released today. See you with 2.49.5 and maybe already on the new infra.
Status: ASSIGNED → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.49
You need to log in before you can comment on or make changes to this bug.