Proposed 2023.2 Bobcat release schedule
This is a proposed release schedule for OpenStack 2023.2 "Bobcat", with a total duration of 28 weeks. Change-Id: I74f77cadd76ea887d8aa5b79251615c78d46aa1a
This commit is contained in:
parent
9a1c42d6a1
commit
41891030e4
@ -1,4 +1,10 @@
|
|||||||
---
|
---
|
||||||
|
- name: bobcat
|
||||||
|
status: future
|
||||||
|
initial-release: 2023-10-04
|
||||||
|
next-phase:
|
||||||
|
status: development
|
||||||
|
date: 2023-03-22
|
||||||
- name: antelope
|
- name: antelope
|
||||||
status: development
|
status: development
|
||||||
slurp: yes
|
slurp: yes
|
||||||
|
14
doc/source/bobcat/highlights.rst
Normal file
14
doc/source/bobcat/highlights.rst
Normal file
@ -0,0 +1,14 @@
|
|||||||
|
================================
|
||||||
|
2023.2 Bobcat Release Highlights
|
||||||
|
================================
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
These are significant changes reported directly from the project teams and
|
||||||
|
have not been processed in any way. Some highlights may be more significant
|
||||||
|
than others. Please do not take this list as a definitive set of highlights
|
||||||
|
for the release until the Open Infrastructure Foundation marketing staff
|
||||||
|
have had a chance to compile a more accurate message out of these changes.
|
||||||
|
|
||||||
|
.. serieshighlights::
|
||||||
|
:series: bobcat
|
||||||
|
|
18
doc/source/bobcat/index.rst
Normal file
18
doc/source/bobcat/index.rst
Normal file
@ -0,0 +1,18 @@
|
|||||||
|
=============
|
||||||
|
2023.2 Bobcat
|
||||||
|
=============
|
||||||
|
|
||||||
|
Projected Release Date: October 4, 2023
|
||||||
|
|
||||||
|
.. toctree::
|
||||||
|
:maxdepth: 1
|
||||||
|
|
||||||
|
schedule
|
||||||
|
|
||||||
|
.. toctree::
|
||||||
|
:hidden:
|
||||||
|
|
||||||
|
highlights
|
||||||
|
|
||||||
|
.. deliverable::
|
||||||
|
:series: bobcat
|
203
doc/source/bobcat/schedule.rst
Normal file
203
doc/source/bobcat/schedule.rst
Normal file
@ -0,0 +1,203 @@
|
|||||||
|
==============================
|
||||||
|
2023.2 Bobcat Release Schedule
|
||||||
|
==============================
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
Deadlines are generally the Thursday of the week on which they are noted
|
||||||
|
below. Exceptions to this policy will be explicitly mentioned in the event
|
||||||
|
description.
|
||||||
|
|
||||||
|
March 22, 2023 - October 4, 2023 (28 weeks)
|
||||||
|
|
||||||
|
.. datatemplate::
|
||||||
|
:source: schedule.yaml
|
||||||
|
:template: schedule_table.tmpl
|
||||||
|
|
||||||
|
.. ics::
|
||||||
|
:source: schedule.yaml
|
||||||
|
:name: Bobcat
|
||||||
|
|
||||||
|
`Subscribe to iCalendar file <schedule.ics>`_
|
||||||
|
|
||||||
|
Cross-project events
|
||||||
|
====================
|
||||||
|
|
||||||
|
.. _b-1:
|
||||||
|
|
||||||
|
Bobcat-1 milestone
|
||||||
|
------------------
|
||||||
|
|
||||||
|
May 11, 2023 is the Bobcat-1 milestone. See project-specific notes
|
||||||
|
for relevant deadlines.
|
||||||
|
|
||||||
|
.. _b-cycle-trail:
|
||||||
|
|
||||||
|
Bobcat Cycle-Trailing Release Deadline
|
||||||
|
--------------------------------------
|
||||||
|
|
||||||
|
All projects following the cycle-trailing release model must release
|
||||||
|
their Bobcat deliverables by June 1st, 2023.
|
||||||
|
|
||||||
|
.. _b-summit:
|
||||||
|
|
||||||
|
OpenInfra Summit in Vancouver
|
||||||
|
-----------------------------
|
||||||
|
|
||||||
|
From June 13 to June 15, 2023, the OpenStack community will gather in Vancouver
|
||||||
|
for the OpenInfra Summit. Discussions on the future of the software, as well as
|
||||||
|
project team meetings will happen there.
|
||||||
|
|
||||||
|
.. _b-2:
|
||||||
|
|
||||||
|
Bobcat-2 milestone
|
||||||
|
------------------
|
||||||
|
|
||||||
|
July 6, 2023 is the Bobcat-2 milestone. See project-specific notes
|
||||||
|
for relevant deadlines.
|
||||||
|
|
||||||
|
.. _b-mf:
|
||||||
|
|
||||||
|
Membership Freeze
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
Projects must participate in at least two milestones in order to be considered
|
||||||
|
part of the release. Projects made official after the second milestone, or
|
||||||
|
which fail to produce milestone releases for at least one of the first and
|
||||||
|
second milestones as well as the third milestone, are therefore not considered
|
||||||
|
part of the release for the cycle. This does not apply to cycle-trailing
|
||||||
|
packaging / lifecycle management projects.
|
||||||
|
|
||||||
|
.. _b-extra-atc-freeze:
|
||||||
|
|
||||||
|
Extra-ATC freeze
|
||||||
|
----------------
|
||||||
|
|
||||||
|
All contributions to OpenStack are valuable, but some are not expressed as
|
||||||
|
Gerrit code changes. That allow teams to list active contributors to their
|
||||||
|
projects and who do not have a code contribution this cycle, and therefore won't
|
||||||
|
automatically be considered an Active Technical Contributor and allowed
|
||||||
|
to vote. This is done by adding extra-atcs to
|
||||||
|
https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml
|
||||||
|
before the Extra-ATC freeze on August 17, 2023.
|
||||||
|
|
||||||
|
.. _b-final-lib:
|
||||||
|
|
||||||
|
Final release for non-client libraries
|
||||||
|
--------------------------------------
|
||||||
|
|
||||||
|
Libraries that are not client libraries (Oslo and others) should issue their
|
||||||
|
final release during this week. That allows to give time for last-minute
|
||||||
|
changes before feature freeze.
|
||||||
|
|
||||||
|
.. _b-3:
|
||||||
|
|
||||||
|
Bobcat-3 milestone
|
||||||
|
------------------
|
||||||
|
|
||||||
|
August 31, 2023 is the Bobcat-3 milestone. See project-specific notes
|
||||||
|
for relevant deadlines.
|
||||||
|
|
||||||
|
.. _b-ff:
|
||||||
|
|
||||||
|
Feature freeze
|
||||||
|
--------------
|
||||||
|
|
||||||
|
The Bobcat-3 milestone marks feature freeze for projects following the
|
||||||
|
`release:cycle-with-rc`_ model. No featureful patch should be landed
|
||||||
|
after this point. Exceptions may be granted by the project PTL.
|
||||||
|
|
||||||
|
.. _release:cycle-with-rc: https://releases.openstack.org/reference/release_models.html#cycle-with-rc
|
||||||
|
|
||||||
|
.. _b-final-clientlib:
|
||||||
|
|
||||||
|
Final release for client libraries
|
||||||
|
----------------------------------
|
||||||
|
|
||||||
|
Client libraries should issue their final release during this week, to match
|
||||||
|
feature freeze.
|
||||||
|
|
||||||
|
.. _b-soft-sf:
|
||||||
|
|
||||||
|
Soft StringFreeze
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
You are no longer allowed to accept proposed changes containing modifications
|
||||||
|
in user-facing strings. Such changes should be rejected by the review team and
|
||||||
|
postponed until the next series development opens (which should happen when RC1
|
||||||
|
is published).
|
||||||
|
|
||||||
|
.. _b-rf:
|
||||||
|
|
||||||
|
Requirements freeze
|
||||||
|
-------------------
|
||||||
|
|
||||||
|
After the Bobcat-3 milestone, only critical requirements and constraints
|
||||||
|
changes will be allowed. Freezing our requirements list gives packagers
|
||||||
|
downstream an opportunity to catch up and prepare packages for everything
|
||||||
|
necessary for distributions of the upcoming release. The requirements remain
|
||||||
|
frozen until the stable branches are created, with the release candidates.
|
||||||
|
|
||||||
|
.. _b-rc1:
|
||||||
|
|
||||||
|
RC1 target week
|
||||||
|
---------------
|
||||||
|
|
||||||
|
The week of September 11, 2023 is the target date for projects following the
|
||||||
|
`release:cycle-with-rc`_ model to issue their first release candidate.
|
||||||
|
|
||||||
|
.. _b-hard-sf:
|
||||||
|
|
||||||
|
Hard StringFreeze
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
This happens when the RC1 for the project is tagged. At this point, ideally
|
||||||
|
no strings are changed (or added, or removed), to give translators time to
|
||||||
|
finish up their efforts.
|
||||||
|
|
||||||
|
.. _b-finalrc:
|
||||||
|
|
||||||
|
Final RCs and intermediary releases
|
||||||
|
-----------------------------------
|
||||||
|
|
||||||
|
The week of September 25, 2023 is the last week to issue release
|
||||||
|
candidates or intermediary releases before release week. During release week,
|
||||||
|
only final-release-critical releases will be accepted (at the discretion of
|
||||||
|
the release team).
|
||||||
|
|
||||||
|
.. _b-final:
|
||||||
|
|
||||||
|
Bobcat release
|
||||||
|
--------------
|
||||||
|
|
||||||
|
The Bobcat coordinated release will happen on Wednesday, October 4, 2023.
|
||||||
|
|
||||||
|
.. _b-cycle-highlights:
|
||||||
|
|
||||||
|
Cycle Highlights
|
||||||
|
----------------
|
||||||
|
|
||||||
|
Cycle highlights need to be added to the release deliverables after the
|
||||||
|
feature freeze to be included in any marketing release messaging.
|
||||||
|
Highlights may be added after this point, but they will likely only be
|
||||||
|
useful for historical purposes.
|
||||||
|
|
||||||
|
See the `Project Team Guide`_ for more details and instructions on adding
|
||||||
|
these highlights.
|
||||||
|
|
||||||
|
For examples of previous release highlights:
|
||||||
|
`Stein Highlights <https://releases.openstack.org/stein/highlights.html>`_,
|
||||||
|
`Train Highlights <https://releases.openstack.org/train/highlights.html>`_,
|
||||||
|
`Ussuri Highlights <https://releases.openstack.org/ussuri/highlights.html>`_,
|
||||||
|
`Victoria Highlights <https://releases.openstack.org/victoria/highlights.html>`_,
|
||||||
|
`Wallaby Highlights <https://releases.openstack.org/wallaby/highlights.html>`_,
|
||||||
|
`Xena Highlights <https://releases.openstack.org/xena/highlights.html>`_,
|
||||||
|
`Yoga Highlights <https://releases.openstack.org/yoga/highlights.html>`_,
|
||||||
|
`Zed Highlights <https://releases.openstack.org/zed/highlights.html>`_.
|
||||||
|
|
||||||
|
.. _Project Team Guide: https://docs.openstack.org/project-team-guide/release-management.html#cycle-highlights
|
||||||
|
|
||||||
|
|
||||||
|
Project-specific events
|
||||||
|
=======================
|
||||||
|
|
120
doc/source/bobcat/schedule.yaml
Normal file
120
doc/source/bobcat/schedule.yaml
Normal file
@ -0,0 +1,120 @@
|
|||||||
|
---
|
||||||
|
start-week: 2023-03-27
|
||||||
|
release-week: 2023-10-02
|
||||||
|
cycle:
|
||||||
|
- end: '2023-03-24'
|
||||||
|
start: '2023-03-20'
|
||||||
|
x-project:
|
||||||
|
- a-final
|
||||||
|
- end: '2023-03-31'
|
||||||
|
name: R-27
|
||||||
|
start: '2023-03-27'
|
||||||
|
- end: '2023-04-07'
|
||||||
|
name: R-26
|
||||||
|
start: '2023-04-03'
|
||||||
|
- end: '2023-04-14'
|
||||||
|
name: R-25
|
||||||
|
start: '2023-04-10'
|
||||||
|
- end: '2023-04-21'
|
||||||
|
name: R-24
|
||||||
|
start: '2023-04-17'
|
||||||
|
- end: '2023-04-28'
|
||||||
|
name: R-23
|
||||||
|
start: '2023-04-24'
|
||||||
|
- end: '2023-05-05'
|
||||||
|
name: R-22
|
||||||
|
start: '2023-05-01'
|
||||||
|
- end: '2023-05-12'
|
||||||
|
name: R-21
|
||||||
|
start: '2023-05-08'
|
||||||
|
x-project:
|
||||||
|
- b-1
|
||||||
|
- end: '2023-05-19'
|
||||||
|
name: R-20
|
||||||
|
start: '2023-05-15'
|
||||||
|
- end: '2023-05-26'
|
||||||
|
name: R-19
|
||||||
|
start: '2023-05-22'
|
||||||
|
- end: '2023-06-02'
|
||||||
|
name: R-18
|
||||||
|
start: '2023-05-29'
|
||||||
|
x-project:
|
||||||
|
- b-cycle-trail
|
||||||
|
- end: '2023-06-09'
|
||||||
|
name: R-17
|
||||||
|
start: '2023-06-05'
|
||||||
|
- end: '2023-06-16'
|
||||||
|
name: R-16
|
||||||
|
start: '2023-06-12'
|
||||||
|
x-project:
|
||||||
|
- b-summit
|
||||||
|
- end: '2023-06-23'
|
||||||
|
name: R-15
|
||||||
|
start: '2023-06-19'
|
||||||
|
- end: '2023-06-30'
|
||||||
|
name: R-14
|
||||||
|
start: '2023-06-26'
|
||||||
|
- end: '2023-07-07'
|
||||||
|
name: R-13
|
||||||
|
start: '2023-07-03'
|
||||||
|
x-project:
|
||||||
|
- b-2
|
||||||
|
- b-mf
|
||||||
|
- end: '2023-07-14'
|
||||||
|
name: R-12
|
||||||
|
start: '2023-07-10'
|
||||||
|
- end: '2023-07-21'
|
||||||
|
name: R-11
|
||||||
|
start: '2023-07-17'
|
||||||
|
- end: '2023-07-28'
|
||||||
|
name: R-10
|
||||||
|
start: '2023-07-24'
|
||||||
|
- end: '2023-08-04'
|
||||||
|
name: R-9
|
||||||
|
start: '2023-07-31'
|
||||||
|
- end: '2023-08-11'
|
||||||
|
name: R-8
|
||||||
|
start: '2023-08-07'
|
||||||
|
- end: '2023-08-18'
|
||||||
|
name: R-7
|
||||||
|
start: '2023-08-14'
|
||||||
|
x-project:
|
||||||
|
- b-extra-atc-freeze
|
||||||
|
- end: '2023-08-25'
|
||||||
|
name: R-6
|
||||||
|
start: '2023-08-21'
|
||||||
|
x-project:
|
||||||
|
- b-final-lib
|
||||||
|
- end: '2023-09-01'
|
||||||
|
name: R-5
|
||||||
|
start: '2023-08-28'
|
||||||
|
x-project:
|
||||||
|
- b-3
|
||||||
|
- b-ff
|
||||||
|
- b-final-clientlib
|
||||||
|
- b-soft-sf
|
||||||
|
- b-rf
|
||||||
|
- b-cycle-highlights
|
||||||
|
- end: '2023-09-08'
|
||||||
|
name: R-4
|
||||||
|
start: '2023-09-04'
|
||||||
|
- end: '2023-09-15'
|
||||||
|
name: R-3
|
||||||
|
start: '2023-09-11'
|
||||||
|
x-project:
|
||||||
|
- b-rc1
|
||||||
|
- b-hard-sf
|
||||||
|
- end: '2023-09-22'
|
||||||
|
name: R-2
|
||||||
|
start: '2023-09-18'
|
||||||
|
- end: '2023-09-29'
|
||||||
|
name: R-1
|
||||||
|
start: '2023-09-25'
|
||||||
|
x-project:
|
||||||
|
- b-finalrc
|
||||||
|
- end: '2023-10-06'
|
||||||
|
name: R+0
|
||||||
|
start: '2023-10-02'
|
||||||
|
x-project:
|
||||||
|
- b-final
|
||||||
|
|
@ -22,6 +22,7 @@ updates.
|
|||||||
:maxdepth: 1
|
:maxdepth: 1
|
||||||
:hidden:
|
:hidden:
|
||||||
|
|
||||||
|
bobcat/index
|
||||||
antelope/index
|
antelope/index
|
||||||
zed/index
|
zed/index
|
||||||
yoga/index
|
yoga/index
|
||||||
|
Loading…
x
Reference in New Issue
Block a user