In an effort to keep an eye on what's going on on various branches, we now have *status-** flags, just as we do for Firefox on Android.
Aaron et al, please make the effort to set these — mainly to distinguish bugs on master (Swift 2.0) from bugs on the v1 branch. E.g., status-fxios-1.0.5=affected means a bug affects 1.0.5. When you uplift that work to the v1 branch, mark that as =fixed. When QA verifies in TestFlight, we can flip it to =verified. These flags allow us to keep track of backports: set both -1.1 and -1.0.5 if a patch needs to land in both places, and flip as you land. (For the old Androiders: no target-milestone: we don't really have the same concept of trains.) We also now have an explicit *tracking-fxios* field for *1.0.5* (as well as future releases). That means we no longer need *+*, so we can relegate that to its historical use as "bugs of interest". I've updated the triage page to include the releases for the rest of the year, as well as plain ol' +: https://wiki.mozilla.org/Mobile/Triage#iOS_Triage_Nominations Any questions? Fire away.
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
