ubuntu-translations-coordinators team mailing list archive

[David Planella <david.planella@xxxxxxxxxx>]

Hi translators,

I'm forwarding a conversation with pitti this morning on
#ubuntu-desktop, just FYI.

td;lr We're updating Maverick and Lucid Firefox to version 9. This will
require a one-off change to those distro's language packs to decouple
them from Firefox translations, which will now be updated in their own
packages, in the same way it's already done from Natty onwards. This
will also mean we'll need to ship an update for _all_ Maverick and Lucid
language packs.

<pitti> dpm: FYI, disabling langpack cronjobs for my preparation of the
lucid/maverick -base refresh (for firefox updates)
<dpm> thanks for the heads up, pitti
<pitti> dpm: we'll need to copy all packs to -updates this time (at
least those which previously had firefox translations), so I'll keep the
same 20110618 snapshot that we already have in maverick-proposed/-updats
<dpm> pitti, ack. Now that we're doing more frequent FF updates that
require all langpacks to be moved to -updates to prevent regressions
(i.e. untranslated Firefoxes), we should perhaps start a discussion on
how we test updates. On the one hand we've got regular updates for which
we require a signoff and FF-related updates, which we do regardless of
signoff. I'll start a thread in the translators list, but do you have
any ideas on how to have a unified way
  of testing/updating langpacks in the meantime?
<pitti> dpm: this is an one-time change for langpacks
 dpm: they move the firefox translations out of the langpacks
themselves, in favour of separate firefox-l10-XX packages
 dpm: we alrady have that in natty/oneiric/precise, but lucid/maverick
get the same change now because we upgrade their firefox from 3.6 to 8
(or whichever version)
 dpm: that's why I don't want to couple them with actual new LP
translation data, just rebuild
<dpm> pitti, ah, gotcha, I had forgotten we did the change from natty
onwards
 pitti, when is the update to FF 8 for maverick and lucid planned?
<pitti> dpm: should hit -proposed for the weekend
<pitti> (both firefox and langpacks)
<micahg> dpm: FF9, i'll fwd you the e-mail I sent earlier
<pitti> dpm: and to -updates Jan 10
<dpm> thanks micahg and pitti

-------- Original Message --------
Subject: 	Firefox Rapid Release migration timetable and plan for
Lucid/Maverick
Date: 	Tue, 13 Dec 2011 01:45:28 -0600
From: 	Micah Gersten <micah.gersten@xxxxxxxxxxxxx>
To: 	Kate Stewart <kate.stewart@xxxxxxxxxxxxx>, Martin Pitt
<martin.pitt@xxxxxxxxxx>
CC: 	Steve Magoun <steve.magoun@xxxxxxxxxxxxx>, Alex Chiang
<alex.chiang@xxxxxxxxxxxxx>, Etienne Goyer
<etienne.goyer@xxxxxxxxxxxxx>, Gary Ekker <gary.ekker@xxxxxxxxxxxxx>,
Jason Warner <jason.warner@xxxxxxxxxxxxx>, Chris Coulson
<chris.coulson@xxxxxxxxxxxxx>, Ubuntu Security <security@xxxxxxxxxx>


2011/12/13 - 2011/12/16 [pitti] pre-prepares for langpack updates for
lucid/maverick
2011/12/13 - 2011/12/16 [micahg] prepares Firefox 9 updates in
ubuntu-security-proposed PPA including addons
2011/12/14 - [micahg] sends notice to ubuntu-security-announce and
ubuntu-announce about the upcoming Firefox change in Lucid/Maverick with
review/approval from skaet and mdeslaur
2011/12/16 - 2011/12/18 [pitti] has langpacks build over the weekend
2011/12/21 - [micahg] does a quick sanity check on the packages before
sending out a call for testing
2012/01/03 - 2012/01/06 - [micahg] QA updates (maybe even with the help
of QA :))
2012/01/10 - [micahg w/AA help] release Firefox 9 and friends to
lucid-updates and maverick-updates
2012/01/31 - [micahg] release Firefox 10 and friends to lucid-security
and maverick-security (provide 3.6 in a PPA for ESR consumers if needed)

2012/01/17 is the cutoff, if we cannot migrate to lucid-updates and
maverick-updates before this date, we'll retry this with Firefox 10 in
-proposed starting on Jan 31 (we won't need the langpacks to be regenerated)

---------------------------------------------------
Possible contingencies:
1. Integration issues found that prevent migration before Jan 17, 2012.

In this case, we simply leave the packages in -proposed and continue
working on fixing issues.  A new round of testing would begin Jan 31
with the Firefox 10 upload in -proposed.

2. Integration issues found after packages migrate to -updates.

If these are severe enough, we can continue to push 3.6 through the
security pocket until we're satisfied with the quality of Firefox Rapid
Release in -updates.
---------------------------------------------------

Please let me know if you see any issues with this plan.

Thanks,
Micah


-- 
Micah Gersten
Ubuntu Security Team



-- 
David Planella
Ubuntu Translations Coordinator
www.ubuntu.com / www.davidplanella.wordpress.com
www.identi.ca/dplanella / www.twitter.com/dplanella

Attachment: signature.asc
Description: OpenPGP digital signature