1.0 L10n Release Certification Process

ゲスト

* When will we get a chance to certify 1.0 final builds?

Very soon! As mentioned above, we're code complete in /cvsroot
which means that we can focus on l10n builds and finalizing l10n changes themselves.
With the latest modifications to the build systems, once a day a release build cycle occurs
which overwrites the files in latest-0.11-l10n for each platform.
Since we want to exercise more control over when this process
will occur than the current automation allows,
we'll push the l10n release builds by hand at schedule intervals over the next couple of days.

Each of these release build runs will provide you and the members of your l10n team
a window of opportunity to finalize changes to your locale and verify a 1.0 final build for your locale. Each of the l10n build machines (Win32, Mac, and Linux) will kick off
a release build run at the following times (Pacific Standard Time):

- Saturday, November 6, 2004 at 17:00
- Sunday, November 7, 2004 at 15:00
- Monday, November 8, 2004 at 10:00

This schedule will give everyone more time to verify their l10n builds on all 3 platforms
before our final release is issued.
The builds usually finish within 2 to 3 hours of being started,
after which you will be able to find new locale builds in latest-0.11-l10n.
As described in Ben Goodger's email sent yesterday,
those builds that have received sign-off by our official release time
will be made available at the same time as the en-US release in our official release directory.

If you are satisfied with a build in latest-0.11-l10n generated from any
of the build runs above and want to sign off on it, please:

1) Save the builds you're certifying locally. I'm going to be juggling a *lot* of files
over the next three days.
By having you save copies of files just in case,
we'll ensure nothing falls on the floor by accident.

2) Post a message signing off on the build and your locale's code
in /l10n to npm.l10n and cc cmp@mozilla.org.

We hope that three release build runs should be enough
to shake out final issues in your localization before we issue our 1.0 release to the public.
Even if you can't sign-off on your locale prior to the 1.0 release,
there's still the opportunity to do so in a later build since after Monday
we'll go back to the normal once-a-day release build runs across all platforms for l10n.

Again, thanks for all of your efforts and helping us find the rough spots in our process
along with the suggestions you've given for ways to improve it
-- they're already helping us prepare for future releases!