4 ms·
From a code maintainance point of view, how do you manage to keep this 'branch' in track with the main one ? I mean, every patch made to the real firefox has to
by ritonlajoie 13y ago
From a code maintainance point of view, how do you manage to keep this 'branch' in track with the main one ?
I mean, every patch made to the real firefox has to be carefully reviewed and backported to this multiprocess branch.
Is that a manual process ? Or can it be automated like that :
1) Check if new commit arrived on 'head'
2) Auto backport it to the multiprocess branch
3) Try a build + run tests. Everything looks good ? Keep it
4) Not goot ? Send an email to the multiprocess maintainer so that he has a look ?
Is there another way to do that ?
- RunningDroid 13y agoThe multiprocess code is in the main branch, just not enabled by default.
- coyotebush 13y agoSince multiprocess is in the regular Nightly, the code is in the main line of development (mozilla-central). Based on the preference, it decides at runtime how to handle the content/chrome interface. But when Mozilla does branch off separate trees, VCS merges and lots of automated tests are largely sufficient.