5 This page explains how the OpenDaylight release process works once the TSC has
11 After release candidate is built gpg sign artifacts using odlsign-bulk script in
12 **releng/builder/scripts**.
17 ./odlsign-bulk STAGING_REPO_ID # eg. autorelease-1367
19 Verify the distribution-karaf file with the signature.
23 gpg2 --verify distribution-karaf-x.y.z-${RELEASE}.tar.gz.asc distribution-karaf-x.y.z-${RELEASE}.tar.gz
26 Releasing OpenDaylight
27 ======================
29 - Block submit permissions for registered users and elevate RE's committer
33 .. figure:: images/gerrit-update-committer-rights.png
37 Enable **Exclusive** checkbox for the submit button to override any
38 existing persmissions. Code-Review and Verify permissions are only needed
39 during version bumping. DO NOT enable it during code freeze.
41 - Nexus: click release for staging repo
44 - Nexus: click release for gpgsign repo (created above in Preparations)
47 - Pull latest autorelease repository
48 **(Release Engineering Team)**
50 .. note:: If you already cloned autorelease the clone line can be skipped below.
54 git clone --recursive https://git.opendaylight.org/gerrit/releng/autorelease
56 git submodule update --init
58 git submodule foreach 'git review -s'
60 - Make sure the latest lftools is installed
61 **(Release Engineering Team)**
63 .. note:: If you already created an lftools virtualenv you can skip the mkvirtualenv step below.
69 pip install --upgrade lftools
71 - Publish release tags
72 **(Release Engineering Team)**
76 export RELEASE=Beryllium-SR4
77 export STREAM=${RELEASE//-*}
79 export PATCH_URL="https://logs.opendaylight.org/releng/jenkins092/autorelease-release-${STREAM,,}/${BUILD_NUM}/archives/patches.tar.gz"
80 ./scripts/release-tags.sh "${RELEASE}" /tmp/patches "$PATCH_URL"
82 - Run autorelease-version-bump-${STREAM} job
83 **(Release Engineering Team)**
85 - Send email to Helpdesk with binary URL to update website
88 - Send email to TSC and Release mailing lists announcing release binaries location
89 **(Release Engineering Team)**
91 - Merge all patches generated by the job
92 **(Release Engineering Team)**
94 - Re-enable submit permissions for registered users and disable elevated RE
95 committer rights on gerrit
98 - Send email to release/tsc/dev notifying tagging and version bump complete
99 **(Release Engineering Team)**
101 - Run autorelease-generate-release-notes-${STREAM} job
102 **(Release Engineering Team)**
104 This job is run a the end of every autorelease build can be used only for
105 service releases (SR). The release notes file (release_notes.rst) is available
106 under archives. For major releases (Nitrogen, Carbon) the docs repository has
107 to branched and published which is only done after release reviews are
110 Release notes can also be manually generated with the script.
114 git checkout stable/${BRANCH,,}
115 cd scripts/release_notes_management/ && ./build.sh
117 The output file (release_notes.rst) generated by the build script is available
118 under autorelease/scripts/release_notes_management/projects/.