Confirmed users
563
edits
NSS/Release Management: Difference between revisions
added magic keyword required for upgrading NSS in m-c
m (adding NSS category) |
(added magic keyword required for upgrading NSS in m-c) |
||
| Line 112: | Line 112: | ||
# For the upgrade task, we have docs https://developer.mozilla.org/en/docs/Updating_NSPR_or_NSS_in_mozilla-central Go to a mozilla-inbound checkout and run the following. | # For the upgrade task, we have docs https://developer.mozilla.org/en/docs/Updating_NSPR_or_NSS_in_mozilla-central Go to a mozilla-inbound checkout and run the following. | ||
#: <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, 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>$ hg push</code> | #: <code>$ hg push</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 | ||