[tor-dev] Tor project automation work

Georg Koppen georg at getfoxyproxy.org
Thu Dec 12 12:26:32 UTC 2013

Nicolas Vigier:
> In addition to this, an other thing that we could do automatically is
> rebasing the tor-browser patches onto the unreleased next mozilla esr
> from http://hg.mozilla.org/releases/mozilla-esr24/ in the default branch.
> This allows to see in advance if rebasing the patches on the next ESR
> release will require some work, and if some new Mozilla patches break
> the build or some tests.

That is definitely a thing high on my wishlist for a while now. If we
could get this going again (there was a time Mike rebased everything for
a new Firefox release) I am all for it. While I am pretty sure rebasing
the patches against the next ESR will require some work (provided we
don't get a substantial portion of them merged upstream meanhwile)
having more time fixing new Firefox issues alone is worth the effort IMO.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20131212/75349789/attachment.sig>

More information about the tor-dev mailing list