NSS/Release Management: Difference between revisions

Jump to navigation Jump to search
RelEng doesn't take care of the NSS release for now
(→‎[NSS Team] Prepare the release: Include release notes)
(RelEng doesn't take care of the NSS release for now)
Line 39: Line 39:
You may have to search [https://treeherder.mozilla.org/#/jobs?repo=nss the prior jobs in treeherder] to find the relevant branch.
You may have to search [https://treeherder.mozilla.org/#/jobs?repo=nss the prior jobs in treeherder] to find the relevant branch.


===== [NSS Team] Prepare a beta =====
===== Prepare a beta =====
# Make sure the beta tags are there in <code>lib/nss/nss.h, lib/softoken/softkver.h, lib/util/nssutil.h</code>
# Make sure the beta tags are there in <code>lib/nss/nss.h, lib/softoken/softkver.h, lib/util/nssutil.h</code>
# If the branch hasn't been made yet, make it
# If the branch hasn't been made yet, make it
Line 50: Line 50:
#: <code>$ hg push --new-branch</code>
#: <code>$ hg push --new-branch</code>


===== [NSS Team] Prepare the release =====
===== Prepare the release =====


# Make sure that the release notes are in NSS before the release
# Make sure that the release notes are in NSS before the release
Line 74: Line 74:
#: <code>$ hg push</code>
#: <code>$ hg push</code>


===== [NSS Team] 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.)
# 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>
Line 83: Line 83:
## <code>$ hg push</code>
## <code>$ hg push</code>


===== [RelEng Team] Create the NSS release archive =====
===== Create the NSS release archive =====
# Make sure you have a stage directory next to the NSS dir.
# Make sure you have a stage directory next to the NSS dir.
#: <code>$ mkdir stage</code>
#: <code>$ mkdir stage</code>
Line 92: Line 92:
#: <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>


===== [RelEng Team] Some additional check one may want to perform =====
===== Some additional check one may want to perform =====
This section is only for the paranoid, only in case you want to double-check that the created file is correct.
This section is only for the paranoid, only in case you want to double-check that the created file is correct.


Line 103: 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.


===== [RelEng Team] Upload release to public ftp/amazon s3. =====
===== Upload release to public ftp/amazon s3. =====
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 126: Line 126:
#: <code>$ aws s3 ls s3://net-mozaws-prod-delivery-contrib/pub/security/nss/releases/NSS_3_26_RTM/src/</code>
#: <code>$ aws s3 ls s3://net-mozaws-prod-delivery-contrib/pub/security/nss/releases/NSS_3_26_RTM/src/</code>


===== [RelEng/SecEng Teams] Upgrading mozilla-central (automated) =====
===== Upgrading mozilla-central (automated) =====
#: RelEng to Uplift the new RTM tag using the [https://github.com/mozilla/nss-tools/ nss-uplift scripts].
#: 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
#: 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
73

edits

Navigation menu