Re: Stable l10n releases off hg repos

[Axel Hecht]

Per today's product meeting and given that we have support for this from
releng and other l10n stake holders, this is how we're going to do it.

Note, the tree rules to need reviews on changes to search and
region.properties won't be affected by this change.

Axel

Axel Hecht wrote:
> Hi,
>
> triggered by a discussion in .l10n, I got thinking about how we want to
> do stable l10n builds (3.1.1) on mercurial.
>
> This is in particular interesting as we're going to have different tree
> policies for various directories inside the releases/l10n-mozilla-1.9.1
> repos.
>
> On CVS, we used to have one date for all locales, and tag that. Now,
> we're not using dates for hg, but source stamps, which offers an
> interesting alternative, IMHO.
>
> I propose to:
>
> - drop the different tree rules for stable/non-stable
> - use an unchanged l10n-changesets file for stable releases by default
> - get localizers to file bugs to update the release changeset instead of
> filing a bug for each patch
>
> We would then just review the total patch from the old changeset to the
> new, make sure that the builds for that changeset are green (*), and
> either request a follow up patch to fix issues, or change the sourcestamp.
>
> (*) I assume here that we're still building the head of default outside
> of release builds, which is a tad confusing, but OK, IMHO, as the ...pre
> builds don't show what's going into the non-pre build.
>
> I wonder if why we didn't merge shipped-locales and l10n-changesets,
> does anybody remember?
>
> What do you think?
>
> Axel
>
> PS: Followup-To and Reply-To set to tree-management.