Perform l10n signoffs for SeaMonkey 2.1b3

RESOLVED FIXED in seamonkey2.1b3

Status

SeaMonkey
Project Organization
--
blocker
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: Callek, Assigned: Robert Kaiser)

Tracking

Trunk
seamonkey2.1b3

Firefox Tracking Flags

(blocking-seamonkey2.1 b3+)

Details

(Reporter)

Description

7 years ago
+++ This bug was initially created as a clone of Bug #631291 +++

We are about to spin a new comm-2.0 build, and once again need the l10n signoffs performed.

If any locales are added/removed we also need to update shipped-locales in comm-central

I'm still a bit blind on the l10n side of the release management here.

I do notice that https://l10n-stage-sj.mozilla.org/shipping/l10n-changesets?ms=sea2.1b3 is a 404, so not sure specifically what needs to be done on this end or by whom, but Filing now so we can be sure it is done, and ready to go for a spin by midnight (EDT) [9pm Monday PDT]
(Assignee)

Comment 1

7 years ago
I probably do need to do the sign-offs, as Adrian doesn't have access to do that on the dashboard right now - I don't know if I still get around to doing that today, though, I'm still trying to get on top of my unread email...

As for the changesets file not being available - apparently 1) I messed up and never marked Beta 2 as "shipped" on the dashboard, 2) because of that never remembered to ask Pike for creating a Beta 3 milestone there and 3) he probably won't be fast to react because he's out partying in Las Vegas until some time tomorrow. Still, Axel, when you're reading this, could you do it?

We really need to go through me doing sign-offs for Beta 3, though, as we probably have some locales being completely broken by the Chatzilla changes which we can't merge. Sorry, I should have checked that before. :(
(Assignee)

Comment 2

7 years ago
I can sign off those locales with those versions for 2.1b3 at this moment:

be 0436e4c78cbc
cs 29d9c7653a4c
de 9928e131e3eb
es-AR 7260c60dba44
es-ES d32c6c3794a4
fi 8aa5d2d14768
fr 8b23fb1e2008
lt 87e6b3f0d6cd
nb-NO 7e218bee5533
nl 67c0d6bf75f5
pl ee36c1b741d9
pt-PT 1d845feb5201
ru 16416eec73c1
sk 85172039be85
sv-SE f9fa76a38aa3


Italian can't be signed off at this moment because ChatZilla brokenness causes builds to go green. Others have not requested a sign-off on l10n-mozilla-2.0 yet.
(Assignee)

Comment 3

7 years ago
OK, we agreed to go with this set, CCing prometeo so he knows we unfortunately need to exclude Italian for this beta - there's still enough time to jump on the RC/final train, of course.
Assignee: nobody → kairo
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.1b3
(Reporter)

Updated

7 years ago
Blocks: 647928

Comment 4

7 years ago
I'd suggest renaming beta 2 to beta 3, and then hit the ship-it button on that for the b3 status. Recreating correct data for b2 is gonna be hard, I'd rather just leave it non-existant in that case.
(Reporter)

Comment 5

7 years ago
If that has to be done from your end [the rename] consider it ok from me to do that. Thank You.
(Reporter)

Comment 6

7 years ago
KaiRo, we do have a slight issue.

Not all of your signed off locales passed :( [due to cZ changes]

Failed locales:

* nb-NO
* fi
* sv-SE

I do not think I am going to be respinning for these, but want your ok that losing these locales (+ `it`) is ok for b3.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 7

7 years ago
I think those are still signed off with changesets from before that cZ checkin, and I only checked new signoff requests for problems, of which "it" was one.
(Assignee)

Comment 8

7 years ago
(In reply to comment #4)
> I'd suggest renaming beta 2 to beta 3, and then hit the ship-it button on that
> for the b3 status. Recreating correct data for b2 is gonna be hard, I'd rather
> just leave it non-existant in that case.

Axel, yes, that sounds good, let's go with it.
(Reporter)

Updated

7 years ago
Status: REOPENED → RESOLVED
Last Resolved: 7 years ago7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.