Confirmed users
425
edits
Line 77: | Line 77: | ||
# As mentioned above, if you can complete an uplift yourself, by creating a pull request, rather than simply flagging a bug as affected, that is preferable. | # As mentioned above, if you can complete an uplift yourself, by creating a pull request, rather than simply flagging a bug as affected, that is preferable. | ||
# Monitor bugs that are flagged as ''status-b2g-v1.2: affected'', and complete the uplifts for those. You can use a [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=gaia-ui-test-open-v1.2-affected&sharer_id=440009&list_id=8605601 shared Bugzilla query] that was created for this purpose to view such bugs. | # Monitor bugs that are flagged as ''status-b2g-v1.2: affected'', and complete the uplifts for those. You can use a [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=gaia-ui-test-open-v1.2-affected&sharer_id=440009&list_id=8605601 shared Bugzilla query] that was created for this purpose to view such bugs. | ||
# Complete | # Complete a manual audit of commits that have landed in master but not v1.2. This is something that should be done once or twice per month. | ||
## | ## Generate a list of all the commits that have landed in master but not v1.2 using this command: <code>git show master ^v1.2 --no-merges -- tests/python/gaia-ui-tests</code>. | ||
## Go through the list and verify whether any of those commits need to be uplifted to v1.2. | |||
### Some will not require uplifting because they are not applicable to v1.2. | |||
### Some of the changes may already be in v1.2, but were added using different commits (e.g, via a cherry pick which resulted in conflicts). | |||
### For any that you find that do need to be uplifted to v1.2, reopen the bug to which the original pull request was added and either: | |||
#### Complete the uplift yourself by opening a pull request for v1.2 and attaching it to the bug, or | |||
#### Flag it as ''status-b2g-v1.2: affected''. |