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