75
edits
NSS/Release Management: Difference between revisions
Jump to navigation
Jump to search
→Upgrading mozilla-central (manual instructions): Fix the moz-phab submit step
(Change upload instructions following switch to google cloud) |
Beurdouche (talk | contribs) (→Upgrading mozilla-central (manual instructions): Fix the moz-phab submit step) |
||
| Line 145: | Line 145: | ||
#: <code>$ python client.py update_nss NSS_3_26_RTM</code> | #: <code>$ python client.py update_nss NSS_3_26_RTM</code> | ||
#: <code>$ hg commit -m "Bug 1216283, land NSS_3_26_RTM, UPGRADE_NSS_RELEASE, r=the-reviewer-name"</code> | #: <code>$ hg commit -m "Bug 1216283, land NSS_3_26_RTM, UPGRADE_NSS_RELEASE, r=the-reviewer-name"</code> | ||
#: <code>$ | #: <code>$ moz-phab submit</code> | ||
# If we must land into branches, like aurora or beta, we must get approvals, etc. Note that we don't do patches for branch landing. We use a placeholder attachment | # If we must land into branches, like aurora or beta, we must get approvals, etc. Note that we don't do patches for branch landing. We use a placeholder attachment | ||
with the command to be executed. The reason is, that the state of those dependency files might be different between branches (where we upgrade or remove newlines as necessary, to trigger full rebuilds). By using the upgrade script, this is handled automatically. | with the command to be executed. The reason is, that the state of those dependency files might be different between branches (where we upgrade or remove newlines as necessary, to trigger full rebuilds). By using the upgrade script, this is handled automatically. | ||