This tags the final release for all cycle-with-rc projects for Victoria.
While not required, having PTLs ack this patch would be nice to include
that record in the merged metadata.
Release activity should now be frozen until this is processed on Oct 14.
Any bugfixes merged to stable/victoria can be queued up and ready to go
as a follow on stable release after the coordinated release date.
There are different diff-start values for each project. This is used
when generating release notes to denote the point where the
stable/ussuri branch started to diverge from what is included on
stable/victoria. For some, this will be the final Ussuri major version,
but if multiple RCs were done, this may show the initial RC1 release
version. This is normal.
Change-Id: I71d78cf386b960c20f6f453fb13c263d4c9b2e18
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
As a courtesy for project teams, on RC1 week the release management
team proposes a RC1 release for all cycle-with-rc deliverables,
based on HEAD. That RC1 will double as the branch point for the
stable/victoria branch for monasca-events-api.
Release liaison or PTL should +1 this proposal if they are happy
with it, amend this proposal (for example with a more recent SHA)
to match their needs, or -1 to block it until release-critical
issues are all fixed.
Change-Id: Ic1449a87a369f0c1e736c665ae9c07fe2ddbc727
Signed-off-by: Thierry Carrez <thierry@openstack.org>