>> At the risk of wasted work, can we not just have a branch in >> /mozilla/mozilla-central? Same organizational access rights, but master >> would be automatically updated without someone having to pull between forks… > > And how does this relate to ELM? We don't build nightlies from github.
As of this morning I have an action item to write this up, so thank you for prompting me :P Essentially, working in git branches is more pleasant for some than working in Bugzilla. In short: * Fork your own, or share, a GitHub mirror of m-c. * Assign yourself a feature bug. * Create a branch for your work: rnewman/bug-123456. * Work in that branch, and keep it rebased on top of the 'elm' branch, which tracks upstream hg elm (and thus everyone else's landing work). * Do your own local builds, test, whatever. * When you're ready to land: rebase, flatten, upload a patch to Bugzilla (ideally), get review, land in hg, set bug flags. * Automatic tools will ensure that hg elm -> GitHub elm in mere moments, and your next Git branch can rebase on top of the work you just finished. * Eventually, hg elm will merge to hg m-c, and we can continue mainline development in the usual way. The hg alternative: * Assign yourself a feature bug. * Use hg mq to handle one or more patch files implementing your work. * Do your own local builds, test, whatever. * When you're ready to land: rebase, flatten, upload a patch to Bugzilla, get review, land in hg, set bug flags. * Everything else proceeds in the same way. _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
