New policy for syncing mozbase to mozilla-central:

[William Lachance]

In an effort to make applying minor fixes that involve mozbase to
mozilla-central easier, we've adjusted the policy for synchronizing
mozbase to allow for minor patches to be committed directly to
mozilla-central, without going through the full mirroring process we
currently insist on (see below). Apparently this approach has worked
well for the breakpad software that Ted maintains
(https://wiki.mozilla.org/Breakpad), hopefully the experience there will
translate. :)

Keeping mozbase on github in sync with mozilla-central and pypi is still
seen as a desirable goal, so in-tree harnesses (mochitest, reftest,
xpcshell) can be kept in sync with out of tree ones (talos,
mozregression, etc.). Thus, non-trivial changes should still go through
the normal process described here:

https://wiki.mozilla.org/Auto-tools/Projects/MozBase#Mirroring_to_Mozilla-Central

If this new policy turns out to cause more problems than it solves, we
can always revisit and revise. But until further notice, this is the new
policy. Hope it helps people get more work done faster. :)

Happy hacking,

Will

[Ted Mielczarek]

On 5/30/2013 11:53 AM, William Lachance wrote:
> In an effort to make applying minor fixes that involve mozbase to
> mozilla-central easier, we've adjusted the policy for synchronizing
> mozbase to allow for minor patches to be committed directly to
> mozilla-central, without going through the full mirroring process we
> currently insist on (see below). Apparently this approach has worked
> well for the breakpad software that Ted maintains
> (https://wiki.mozilla.org/Breakpad), hopefully the experience there
> will translate. :)

To clarify: the policy is that if you land a patch in the mozbase github
repository, you can also cherry-pick it to land on
mozilla-{central,inbound} without having to do a full mozbase
release/sync. This minimizes the risk of things getting out of sync.

-Ted