If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.
Bug 788983 (SM2.12.1)

Tracking bug for build and release of SeaMonkey 2.12.1

RESOLVED FIXED

Status

SeaMonkey
Release Engineering
P1
blocker
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: ewong, Assigned: ewong)

Tracking

SeaMonkey 2.12 Branch
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(3 attachments, 2 obsolete attachments)

(Assignee)

Description

5 years ago
This is a tracking bug for Build and Release of SeaMonkey 2.12.1

We expect an actual release on Monday 10th September.
(Assignee)

Updated

5 years ago
Depends on: 788984
(Assignee)

Comment 1

5 years ago
Created attachment 659439 [details] [diff] [review]
Update configs for SeaMonkey 2.12.1 (v1)
Assignee: nobody → ewong
Status: NEW → ASSIGNED
Attachment #659439 - Flags: review?(bugspam.Callek)
Comment on attachment 659439 [details] [diff] [review]
Update configs for SeaMonkey 2.12.1 (v1)

Review of attachment 659439 [details] [diff] [review]:
-----------------------------------------------------------------

::: seamonkey/release-comm-release.py
@@ +32,3 @@
>  releaseConfig['relbranchOverride']          = ''
> +#releaseConfig['productVersionFile']         = 'suite/config/version.txt'
> +releaseConfig['productVersionFile']         = ''

I know this swap is what I said in IRC, but this swap for productVersionFile is wrong, r+ if you swap it back
Attachment #659439 - Flags: review?(bugspam.Callek) → review+
(Assignee)

Comment 3

5 years ago
Created attachment 659440 [details] [diff] [review]
Update configs for SeaMonkey 2.12.1 (v2)

Uncommented the productVersionFile line.
Attachment #659439 - Attachment is obsolete: true
Attachment #659440 - Flags: review+
Comment on attachment 659440 [details] [diff] [review]
Update configs for SeaMonkey 2.12.1 (v2)

Review of attachment 659440 [details] [diff] [review]:
-----------------------------------------------------------------

We'll need a build 2, because of...

::: seamonkey/release-comm-release.py
@@ +14,1 @@
>  releaseConfig['appVersion']                 = '2.12'

Turns out we forgot to bump this line, so I was forced to do the bump manually:

remote: You can view your changes at the following URLs:
remote:   https://hg.mozilla.org/releases/comm-release/rev/378bed8d856f
remote:   https://hg.mozilla.org/releases/comm-release/rev/07071556df55
Created attachment 659562 [details] [diff] [review]
Config for Build 2
Attachment #659562 - Flags: review?(ewong)
Created attachment 659563 [details] [diff] [review]
Config for Build 2 - take 2

ewong informed me over irc that I need 'milestone' bumped too, he's right.
Attachment #659562 - Attachment is obsolete: true
Attachment #659562 - Flags: review?(ewong)
Attachment #659563 - Flags: review?(ewong)
(Assignee)

Updated

5 years ago
Attachment #659563 - Flags: review?(ewong) → review+
Created attachment 659617 [details]
patcher config for partial from 2.11 to 2.12.1

r? to ewong, incase he suspects he can understand well enough.

I'm using https://wiki.mozilla.org/SeaMonkey:Release_Process:2.6.1#Updates_from_2.5_to_2.6.1 as my guide on "how?
Attachment #659617 - Flags: review?(ewong)
(Assignee)

Updated

5 years ago
Attachment #659617 - Flags: review?(ewong) → review+
Just pushed the files to mirrors, awaiting website changes to be ready before we push live.
(In reply to Justin Wood (:Callek) from comment #8)
> awaiting website changes to be ready before we push live.

I prepared them locally on Sat already, but now I don't have access to them until at least 9h from now.
Depends on: 789866
(In reply to Jens Hatlak (:InvisibleSmiley) from comment #9)
> I prepared them locally on Sat already, but now I don't have access to them
> until at least 9h from now.

... he said before a thought crossed his mind. Dropbox! :-)
(Assignee)

Updated

5 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Assignee)

Updated

5 years ago
Blocks: 798991
You need to log in before you can comment on or make changes to this bug.