This is a 26 week schedule for the Wallaby release. Planned release date
is April 14, 2021. We don't have a date set for a first half 2021 event,
but it is expected to be some time shortly after this date.
Change-Id: I6ba030f678879d32f99680c68dcd4bff9cc00032
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
As it happened in the past, the Extended Maintenance deadline conflicts
with the Final Release of the actual development cycle. Same way as it
was resolved in that time, postpone the EM deadline by approximately 4
weeks, to a less busy period. Also move the deadline some days to not
to fall to weekend.
Change-Id: I2b502f6b5189bd0f7e6bf0286105ad27da1643c7
Discussions happening about transitioning ocata to EOL. According to our
stable policy, the branch should go through an unmaintained period to
give others an opportunity to step up and maintain things. To make this
explicit, this sets a date to make the overall state of ocata
Unmaintained so there are no surprises if and when we decide to make it
EOL community-wide.
Change-Id: I90fd9fc31464a451cc5476578081061947df9c7a
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Hongbin has two Gerrit accounts (gmail.com and huawei.com),
but seems to use the gmail.com account more in Gerrit. Add
it to the liaison file so that PTL-approval works.
Change-Id: I77ed584610268bf25d089931643cd196f6ded5b9
Project's last releases in Rocky have been tagged with rocky-em,
so let's move Rocky to Extendended Maintenance phase.
Change-Id: I9fbccb70dbb77bbe4ad2dec42dceb09306bf587d
This proposes a 22 week release schedule to align the release right
before the week of the fall Summit event.
Change-Id: I8c4aff8a600773640539db1f88fb0d7ef74024d7
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Adrian Turjak is using a different address for reviews than
the one defined in governance. Add the review address to
the adjutant release liaisons so that check-ptl-approval
works as intended.
Change-Id: I26ac918f66146c7b818e646ce54b2aea84a302ac
Eyal Bar-Ilan is using a different address for reviews than
the one defined in governance. Add the review address to
the Vitrage release liaisons so that check-ptl-approval
works as intended.
Change-Id: I520d75f39ef5f458e085df3f56573af68258811f
Team names in liaison files did not match team name in governance,
creating issues assessing liaisons in check_approval.
Also documentation is no longer a project team, so should be removed
from liaison file.
Change-Id: I33cf559396638054218ba65c8b1f725e47660a71
As I have stepped out, and trained noonedeadpunk for release
business, I now have the impression I can remove this from my belt.
I trust him to do the right thing, and he can ask for my help if
necessary.
Change-Id: I935c855886fd2bef61ef3c23453f06ac2b14955d
I'm no longer active enough with either OSC or Oslo to serve as
release liaison for those projects.
Change-Id: Ibd5edb8bd7507af4c7c80e5908b4c1470d14c392
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Mark has been an ironic contributor for some time,
is an Ironic core, and has assisted with releases
of ironic in the past. As such, we wish to confer
the rights to release ironic as needed
Thank you Mark for being awesome.
Change-Id: Idd4f2833c523dd8b64abe4d556120f4e46e29720
We didn't actually want Train to go immediately into Extended
Maintenance. This fixes the transition date for Train to be 18 months
from its original release date.
Change-Id: I777a468c995c4f90852b9b14f6d188438357bc34
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
If we make Ussuri the future release, the htaccess will be generated
with redirections for it. When we decide that Train is maintained and
not developed, we should move Ussuri to development. And add 'Vancouver'
or something when we know the next series name to immediately generate
the new redirection.
Alternatively, we could change the code to generate the redirections
at all times. If the code is idempotent, we would never have an
issue of "forgotten" state of a series, and could bypass it.
Change-Id: I69008ebd330a90ae42166d55e5c06b694fc2d042
Recent merging of the liaison-loading code in list-changes makes
most list-changes job fail due to error in YAML loading code.
Beyond that YAML loading issue, the code assumes getting a dictionary
with team names as keys and an array of liaisons dictionary as values.
Fix the release_liaisons.yaml and schema to match.
Change-Id: I94fa41862d37aaf0535d64afd00b2bd55bb4649a
As it was discussed during Release Team meeting @ PTG the EM release
should happen somewhere around post release time.
Change-Id: Ibefd2b96cb3409267a8ed6b5e68b5b52255577b6
Adding liaisons to deliverables where there is a liasion listed here:
https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management
Also creates a data dir to put the non deliverable files that were in the
deliverables dir elsewhere and updates filepaths to reflect the change.
Story: 2005702
Task: 31024
Change-Id: Idc5f4b29dd375465b21d678fa8503cbd8d6d3eb6