643216 - (SM2.0.13) Tracking bug for build and release of SeaMonkey 2.0.13

Status: RESOLVED FIXED

(SeaMonkey :: Release Engineering, defect, P1)

Description

[Justin Wood (:Callek)]

+++ This bug was initially created as a clone of Bug #626569 +++

+++ This bug was initially created as a clone of Bug #614274 +++

Looks like firefox may be doing a chemspill, prepping a build of this now.

See: https://wiki.mozilla.org/SeaMonkey:Release_Process:2.0.13

Comment 1

[rsx11m]

You've tagged SEAMONKEY_2_0_12_BUILD1 for changeset FIREFOX_3_5_17_RELEASE, this doesn't look right (and new SM 2.0.12 builds #1 on the ftp site).

Comment 2

[Justin Wood (:Callek)]

(In reply to comment #1)
> You've tagged SEAMONKEY_2_0_12_BUILD1 for changeset FIREFOX_3_5_17_RELEASE,
> this doesn't look right (and new SM 2.0.12 builds #1 on the ftp site).

Thanks, yea, I fixed the ftp for 2.0.12, and Filed Bug 643315 about backing out that tag move for 2.0.12.

(fwiw if I was on the new automation I would have caught that before I kicked off the build itself, but moving to that has not yet happend, sadly.)

p.s. due to that and then not clobbering we had a few repack failures, I manually triggered new repacks for all locales [I thought] then moved on, looks like I missed at least one mac repack (ru) so the mac verifies and update-generation failed, sadly. I'll (tomorrow) re-clobber after the ru repack finishes, and then re-trigger the update-generation and the l10n-verify for mac. And move on. :/

(I'll have a trouble-free release run one of these days.)

Comment 3

[Robert Kaiser]

Pushed the update snippets public.