As discussed in the mail thread [1][2], this patch transition the Rocky
branch to End of Life. The last patch of the branch will be tagged with
rocky-eol tag. stable/rocky branch cannot be used anymore and will be
deleted if this patch merges.
This is needed as stable/rocky is not actively maintained in recent
period, thus gates are mostly broken due to job failures. Besides,
by removing these branches, infra resources will be freed up, too.
Please try to identify any zuul job, that is defined outside of the
repositories in this patch (for example in openstack-zuul-jobs, etc.)
and won't be used anymore if stable/rocky is deleted. Propose a job
removal patch for them.
Please +1 if the team is ready for us to proceed with this transition,
or -1 if there are still some activity on the branch and the team wants
to continue to maintain it.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031922.html
[2] https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033386.html
Change-Id: Ib6f964aad3b1b61f8af942153081cfbd3c05596e
The YAML 1.2 spec was released in 2009. It's probably been enough time
that it's safe to move to it.
The only issue for out YAML usage was 1.2 dropped the use of Yes, No, On,
and Off as valid boolean values.
Change-Id: I608e09d219379e00cca15c5ff165bb63aecfe9f2
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This adds stable/rocky branching for client libraries that missed
branching during the deadline.
Change-Id: Idd10518008d13ac08b4e78598310c2cc9528ded3
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
These files are based on the deliverables that were actually released
during queens.
Change-Id: Ie95848d0f95c41cc6765f2ba07801a0770a8ecdb
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
