On Tue, Nov 21, 2017 at 12:44 PM, Nicolas Vigier boklm@mars-attacks.org wrote:
From your list it seems to me the most challenging part will be to continuously monitor the mozilla changes and be able to find workarounds for all issues in time before each release. But maybe the closer collaboration with Mozilla can help with this.
Yes -- I guess one problem is, when a patch lands in Mozilla central, it will be in a release between 7 and 14 weeks later.
If we go with that plan I think we should also check whether a git branch is still the best way to maintain our patches. I have not been thinking about that a lot yet, but maybe an alternative could be to use quilt [1] or some similar tool to manage patch series. So we could store a quilt patch series as a directory somewhere into tor-browser-build.git, which should make it easier to apply our patches on different firefox trees.
I think that's a very interesting idea.