This is a 25 week schedule for the Xena release. Planned release date
is October 06, 2021.
Change-Id: Ibfaa75d9a567ca981653677ad66763662a2e177f
Signed-off-by: Hervé Beraud <hberaud@redhat.com>
Project's last releases in Stein have been tagged with stein-em.
Now indicate that Stein is in Extended Maintenance phase also at
https://releases.openstack.org
Change-Id: Ibc5139c29ae4b249ee75fa1babccd2d5f58e2767
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 those times, postpone the EM deadline by 4 weeks, to a
less busy period.
Change-Id: I66e4863ac8f3e87ef0a170ac8828f9533db4c3e3
This updates the next phase for the wallaby release to eneter the
"maintained" phase after its planned release on 2021-04-14.
Change-Id: Ieb33e48765bb0601c7232ffb84e493ad23a626e5
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
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>
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>
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
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