If a branch doesn't have any changes on its main code repository or
associated l10n repositories in the last 24 hours, then new builds won't
be triggered.
This also means that no new updates will be published to users on
nightly, aurora or similar channels.
Cheers,
Chris
Axel
What's the easiest way to check for this?
juanb
Axel
_______________________________________________
dev-planning mailing list
dev-pl...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-planning
The concern there is that we would not be triggering new builds when a
locale has no string updates, but en-US has new core changes. That
would leave our testing community outside the US stranded on older
builds where the localizers haven't updated for new strings.
It sounds like that is not the case, and we will get new builds and
updates for all locales that we are actively building on any branch if
core gecko changes.
-chofmann
> Cheers,
> Chris
>
> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=650258
That is correct. If "something" changes, we trigger a full set of builds
and repacks, where "something" include the core source repo (e.g.
mozilla-central) and its associated l10n repos. Only if nothing has
changed (or nothing successfully built in the past 24 hours) do we not
generate any builds or repacks.
I don't have an easy idea, does someone in releng?
Axel
On Wed 20 Jul 2011 04:47:05 PM EDT, Al Billings wrote:
> Are we thinking of doing this for the 1.9.2 branch?
>
> On Jul 18, 2011, at 1:39 PM, Chris AtLee wrote:
>