TripleO Team is no longer accepting patches to
stable/ocata branch, this patch proposes to create ocata-eol
tags for all TripleO projects.
Change-Id: I4dd9715d132af49364b37ad21149fb8b4ab4cd45
During the tag-releases job for the "Tag stable/ocata as extended
maintenance" patch d57f810ad6555528a4af039b693453b551da4cf2, the job
timed out processing all affected repos. There were just a few that need
to have the job run again to push up the tag. This makes a noop change
in those repos to get the tagging to complete.
Change-Id: Iae06ecaca1059bf761d21b91eb5b7e5dd5d2519a
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
According to our extended maintenance documentation [0], we stated at
the start of the extended maintenance phase the "HEAD of the
appropriate branch will be tagged as $series-em", however, we did not
apply these tags to stable/ocata at the time. This adds ocata-em tags to
the ocata deliverables.
[0] https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance
Change-Id: Ibac7f787950bf23e9a75fce37a6b82ec45d7df89
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This reverts commit 8219a384636db694bf3bf8a3edd11d67545f7c7f.
The whole job post-processing failed due to lack of .gitreview in
os-cloud-config's master branch. Let's re-propose it once fixed.
Change-Id: Ieca256ce3b2cbd2f1b60151ef0fcee7389aab9c0
We no longer use the send-announcements-to field for anything.
Change-Id: Ib224c2c94de9e5d8ed2b859157a6850e0f38f4d4
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Update the links for Ocata release notes to use HTTPS and to point to
the series-specific page.
Change-Id: Ib65c70f2760b8fa3cd94ede3ee7b74f9eaecf1d5
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This prepares initial releases for all TripleO components except
tripleo-quickstart (there is some discussion re moving this to
an independent release model as we don't have stable branches
for that because it's a bootstrapping tool, not an end user deliverable)
Note also that I've aligned the puppet-tripleo release naming with the
puppet openstack convention of a number of releases during the
cycle despite being cycle-trailing, but other tripleo components
adopt the 6.0.0.0b1 naming where we're tracking features/bugs
associated with each milestone e.g ref
https://launchpad.net/tripleo/+milestone/ocata-1
Change-Id: I890de6587efcc1ce3d93edcf8dc24e77f67b0d03