Below are a few notes on flags, for all of those interested. Queries can be 
found at https://wiki.mozilla.org/B2G/Triage#Joint_Triage_Queries.

* blocking-basecamp will be deprecated as soon as possible - 
https://bugzilla.mozilla.org/show_bug.cgi?id=830433
* blocking-b2g:tef? is for CRITICAL bug fixes that we'd like to be considered 
for v1.0.0.0 after tomorrow
* blocking-b2g:tef+ is for bugs that we've got agreement with partners about 
needing as part of v1.0.0.0
* tracking-b2g18:+ ensures that it'll be on our radar for the v1 timeframe, and 
tracking-b2g18:? represents a nomination
* tracking-b2g18:19+ ensures that it will be on our radar for the 6 weeks after 
v1.0 code ships (to be fixed prior to FF19's release). This flag will be used 
for security bugs fixed in FF19, for instance.
* status-b2g18 represents the fix status on the v1.* branches

Now for landing.

* v1.0.0.0 Landing
** Gecko: mozilla-b2g18
** Gaia: master branch
** Landing requirements: blocking-b2g:tef+ (representing agreement with 
partners), and approval-gaia-master:+ or approval-mozilla-b2g18:+
* v1.0.1.0 (targeted to be tagged in February)
** Gecko: shira
** Gaia: shira branch
** Landing requirements: blocking-b2g:shira+, or tracking-b2g18:(19)+ with 
driver approval

All Gecko changes committed for v1.* must also land to mozilla-central. The 
shira branch will soon be landed on top of v1 branches, at which point we'll 
deprecate the shira branches. We'll have an update on landing at that time.

-Alex
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to