Create bundles for autorelease post release tagging 63/40063/4
authorThanh Ha <thanh.ha@linuxfoundation.org>
Wed, 8 Jun 2016 17:58:09 +0000 (13:58 -0400)
committerThanh Ha <thanh.ha@linuxfoundation.org>
Thu, 9 Jun 2016 00:29:19 +0000 (20:29 -0400)
commite9cfd468ed342b5422b1e3d214883fdfbc611caa
tree80546ed42bc106d1c5aa3e060b2245320d43ba3a
parent971507be4eccd884e92dd573ac9ec438c2a5f10b
Create bundles for autorelease post release tagging

Start treating all releases as possible release candadites which can be
released at any time the TSC approves a release. All autorelease jobs
will now contain an additional variable *next-release-tag* to signify
the next official release version.

See mailing list discussion thread here:
https://lists.opendaylight.org/pipermail/release/2016-April/006299.html

The release engineer can pull down the bundle files and run:

    git fetch /path/to/project.bundle
    git checkout FETCH_HEAD
    git tag -asm "OpenDaylight [release] release" release/[release]
    git push gerrit release/[release]

To push the build tags to Gerrit. This should cut back on the amount of
patches needing to be pushed to Gerrit for review by half and only the
x.y.z-SNAPSHOT patches need to be pushed.

Change-Id: I53bb95236e41c7e99a12c312e5158db51a9f4e67
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
jjb-templates/validate-autorelease.yaml
jjb/autorelease/autorelease-macros.yaml
jjb/autorelease/autorelease-projects.yaml
jjb/autorelease/autorelease-templates.yaml
jjb/autorelease/include-raw-autorelease-release-versions.sh