Hi all, We're still getting some requests for a simpler explanation of landings/approvals/tracking, so we continue to strive to better explain the process documented at https://wiki.mozilla.org/Release_Management/B2G_Landing. We've come up with an etherpad (45 lines long) to succinctly answer the following core developer questions:
* What important dates/deadlines should I know about? * What's the highest priority bug I should be working on, and how do I find those bugs? * If I find a critical issue, how can I make sure it gets fixed for X? * Where and how should I perform v1.x landings? The etherpad can be found here: https://etherpad.mozilla.org/B2G-Clarifications We're also going to be making a couple of changes to how we track work: 1) We're going to be removing 19+, 20+, 21+, etc. from the Gaia tracking-b2g18 flag, as it's causing confusion and adding little value. These flag values will remain for Gecko security landings. 2) We're going to be changing the blocking-b2g flag into a flag that can have multiple values, since a bug can potentially block multiple partners -Alex _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
