This transition the victoria branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch.
Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.
The transition deadline is April 27th, 2022.
Change-Id: I319a53a43327e32fa0c0bed7e87a960562871112
This release picks up new commits to heat-dashboard since
the last release from stable/victoria.
This is being proposed as a convenience to help make sure stable
changes are being released. If the team is good with this going out,
please respond with a +1 to let the release team know it is OK to
proceed.
If it is not wanted at this time, or if there are more changes that
would be good to get merged before doing a stable release, please
leave a -1 with a comment with what the team would prefer. We can
then either abandon this patch, or wait for an update with a new
commit hash to use instead.
$ git log --oneline --no-merges 4.0.0..02d04ec
02d04ec Imported Translations from Zanata
080771f Run npm nodejs job with Firefox browser
e601aab Move image_field_data method in-tree
85d2a88 Imported Translations from Zanata
44765bb Update TOX_CONSTRAINTS_FILE for stable/victoria
36565ac Update .gitreview for stable/victoria
Signed-off-by: Elod Illes <elod.illes@est.tech>
Change-Id: I7efe2b417d3203586cbd7b6c3e3b27c2dd7f7b73
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 heat-dashboard.
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: Ie28d0830198bdf7c5e9108f8e784f9bbe7738fba
Signed-off-by: Thierry Carrez <thierry@openstack.org>