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 Releasing OpenDaylight
20 ======================
22 - Nexus: click release for staging repo **(Helpdesk)**
23 - Send email to Helpdesk with binary URL to update website **(Helpdesk)**
24 - Send email to TSC and Release mailing lists announcing release binaries location **(Release Engineering Team)**
25 - Checkout autorelease and switch to release branch eg stable/boron
26 **(Release Engineering Team)**
27 - Make sure your git repo is setup to push (use git-review)
33 - Download patches from Jenkins build page
38 wget https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-boron/230/artifact/patches/*zip*/patches.zip
41 - Run the following commands for every project in the release
45 ../scripts/patch-odl-release.sh /tmp/patches Boron
46 git review -y -t Boron
47 git push gerrit release/boron
53 git submodule foreach git checkout release/boron
54 git add [add each project individually to not pull in extra]
55 git commit -sm "Release Boron"
56 git tag -asm "OpenDaylight Boron release" release/boron
57 git review -y -t Boron
58 git push gerrit release/boron
60 - Generate release notes (???)
61 - Send email to release/tsc/dev notifying tagging and version bump complete **(Release Engineering Team)**