75
edits
NSS/Release Management: Difference between revisions
→Upload release to public ftp/google cloud.
(Add commands for creating a beta) |
Beurdouche (talk | contribs) |
||
| (26 intermediate revisions by 5 users not shown) | |||
| Line 51: | Line 51: | ||
===== Prepare the release ===== | ===== Prepare the release ===== | ||
# Make sure that the release notes are in NSS before the release | |||
# Ensure the required NSPR version has been updated | # Ensure the required NSPR version has been updated | ||
## Edit file automation/release/nspr-version.txt and set it to the minimum NSPR version that is required for this NSS release. | ## Edit file automation/release/nspr-version.txt and set it to the minimum NSPR version that is required for this NSS release. | ||
| Line 73: | Line 75: | ||
===== Prepare repo for next version ===== | ===== Prepare repo for next version ===== | ||
# | # On the default branch, increment the version number (to 3.27 in this example) and set the beta flag again. (If you are on the default branch, the beta flag should already be set and only a version increment should happen.) | ||
## <code>$ python automation/release/nss-release-helper.py set_beta</code> | ## <code>$ python automation/release/nss-release-helper.py set_beta</code> | ||
## <code>$ python automation/release/nss-release-helper.py set_version_to_minor_release 3 27</code> | ## <code>$ python automation/release/nss-release-helper.py set_version_to_minor_release 3 27</code> | ||
| Line 86: | Line 88: | ||
# Go to the NSS dir | # Go to the NSS dir | ||
#: <code>$ cd /your/path/to/nss</code> | #: <code>$ cd /your/path/to/nss</code> | ||
# Make sure that the respective NSPR release archive file (for the version listed in automation/release/nspr-version.txt) is contained in your stage directory. (Download it, if you don't have it.) A copy of this NSPR release will be automatically included in the combined NSS release archived. | # Make sure that the respective NSPR release archive file (for the version listed in automation/release/nspr-version.txt) is contained in your stage directory. (Download it, if you don't have it, from https://ftp.mozilla.org/pub/nspr/releases/) A copy of this NSPR release will be automatically included in the combined NSS release archived. It needs to be stored in <code>stage/v<NSPR version number>/src/</code>. | ||
# Run the following command to create two release archive files (<code>nss-3.26.tar.gz</code> and <code>nss-3.26-with-nspr-4.12.tar.gz</code>) and two files SHA1SUMS and SHA256SUMS in <code>/your/path/to/stage/NSS_3_26_RTM/src/</code>. | # Run the following command to create two release archive files (<code>nss-3.26.tar.gz</code> and <code>nss-3.26-with-nspr-4.12.tar.gz</code>) and two files SHA1SUMS and SHA256SUMS in <code>/your/path/to/stage/NSS_3_26_RTM/src/</code>. | ||
#: <code>$ python automation/release/nss-release-helper.py create_nss_release_archive 3.26 NSS_3_26_RTM ../stage</code> | #: <code>$ python automation/release/nss-release-helper.py create_nss_release_archive 3.26 NSS_3_26_RTM ../stage</code> | ||
| Line 101: | Line 103: | ||
# Remove the extracted directory, to ensure you won't upload the individual files. | # Remove the extracted directory, to ensure you won't upload the individual files. | ||
===== Upload release to public ftp/ | ===== Upload release to public ftp/google cloud. ===== | ||
When running the following command ensure that you use the directory name NSS_3_26_RTM twice, both in source and in destination. | When running the following command ensure that you use the directory name NSS_3_26_RTM twice, both in source and in destination. | ||
$ cd /your/path/to/stage | $ cd /your/path/to/stage | ||
| Line 114: | Line 116: | ||
# Check that there's no NSS_3_26_RTM directory at https://ftp.mozilla.org/pub/security/nss/releases/. | # Check that there's no NSS_3_26_RTM directory at https://ftp.mozilla.org/pub/security/nss/releases/. | ||
# Ensure you have | # Ensure you have the gcloud command installed. | ||
# | # (see also: https://cloud.google.com/sdk/docs/install ) | ||
# Upload the release | # Upload the release | ||
#: < | #: <syntaxhighlight> | ||
# Check https://ftp.mozilla.org/pub/security/nss/releases/ (can be delayed | $ NSS_RELEASE=NSS_3_26_RTM \ | ||
GCP_PROJECT=moz-fx-productdelivery-pr-38b5 \ | |||
GCP_ENV=prod; \ | |||
gcloud --project $GCP_PROJECT --impersonate-service-account=nss-team-$GCP_ENV@$GCP_PROJECT.iam.gserviceaccount.com \ | |||
storage cp --recursive --no-clobber $NSS_RELEASE gs://$GCP_PROJECT-productdelivery/pub/security/nss/releases/ | |||
</syntaxhighlight> | |||
# Check https://ftp.mozilla.org/pub/security/nss/releases/ (the indexing of the new directory can be delayed but it can be accessed immediately through the url.) | |||
# Check upload: | # Check upload: | ||
#: <code>$ | #: <code>$ gcloud storage ls gs://moz-fx-productdelivery-pr-38b5-productdelivery/pub/security/nss/releases/</code> | ||
#: <code>$ | #: <code>$ gcloud storage ls gs://moz-fx-productdelivery-pr-38b5-productdelivery/pub/security/nss/releases/NSS_3_26_RTM/</code> | ||
#: <code>$ | #: <code>$ gcloud storage ls gs://moz-fx-productdelivery-pr-38b5-productdelivery/pub/security/nss/releases/NSS_3_26_RTM/src/</code> | ||
===== Upgrading mozilla-central (automated) ===== | |||
#: RelEng to Uplift the new RTM tag using the [https://github.com/mozilla/nss-tools/ nss-uplift scripts]. | |||
#: Amend the uplift commit to set [https://hg.mozilla.org/mozilla-central/log/tip/old-configure.in old-configure.in] file in mozilla-central to point AM_PATH_NSS to the new minimum version of NSS | |||
Example: | |||
PATH=$PATH:/path/to/xpcshell LD_LIBRARY_PATH=/path/to/xpcshell NOBUILD=: /path/to/nss-tools/nss-uplift-unified.sh NSS_X_YY_RTM | |||
===== Upgrading mozilla-central ===== | ===== Upgrading mozilla-central (manual instructions) ===== | ||
# If you already upgraded mozilla-central with the nss-uplift-unified.sh script, you can ignore these manual instructions. | |||
# Someone should approve the upgrade. | # Someone should approve the upgrade. | ||
# 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, 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. | ||
===== Logistics ===== | |||
# Update the [[NSS:Release Versions]] page. | |||
# Update the [https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_Releases MDN NSS Release page]. | |||
[[Category:NSS]] | [[Category:NSS]] | ||