Merge "OpenStack 2024.1 Caracal release schedule"
This commit is contained in:
commit
c9685fc84d
@ -1,4 +1,11 @@
|
||||
---
|
||||
- name: caracal
|
||||
release-id: 2024.1
|
||||
status: future
|
||||
initial-release: 2024-04-03
|
||||
next-phase:
|
||||
status: development
|
||||
date: 2023-10-04
|
||||
- name: bobcat
|
||||
release-id: 2023.2
|
||||
status: development
|
||||
|
@ -41,11 +41,11 @@ for relevant deadlines.
|
||||
|
||||
.. _b-cycle-trail:
|
||||
|
||||
Bobcat Cycle-Trailing Release Deadline
|
||||
--------------------------------------
|
||||
Antelope Cycle-Trailing Release Deadline
|
||||
----------------------------------------
|
||||
|
||||
All projects following the cycle-trailing release model must release
|
||||
their Bobcat deliverables by June 1st, 2023.
|
||||
their Antelope deliverables by June 1st, 2023.
|
||||
|
||||
.. _b-summit:
|
||||
|
||||
|
14
doc/source/caracal/highlights.rst
Normal file
14
doc/source/caracal/highlights.rst
Normal file
@ -0,0 +1,14 @@
|
||||
==================================
|
||||
2024.1 Caracal 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: caracal
|
||||
|
18
doc/source/caracal/index.rst
Normal file
18
doc/source/caracal/index.rst
Normal file
@ -0,0 +1,18 @@
|
||||
===============
|
||||
2024.1 Caracal
|
||||
===============
|
||||
|
||||
Projected Release Date: April 3, 2024
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
schedule
|
||||
|
||||
.. toctree::
|
||||
:hidden:
|
||||
|
||||
highlights
|
||||
|
||||
.. deliverable::
|
||||
:series: caracal
|
202
doc/source/caracal/schedule.rst
Normal file
202
doc/source/caracal/schedule.rst
Normal file
@ -0,0 +1,202 @@
|
||||
================================
|
||||
2024.1 Caracal 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.
|
||||
|
||||
October 5, 2023 - April 3, 2024 (26 weeks)
|
||||
|
||||
.. datatemplate::
|
||||
:source: schedule.yaml
|
||||
:template: schedule_table.tmpl
|
||||
|
||||
.. ics::
|
||||
:source: schedule.yaml
|
||||
:name: Caracal
|
||||
|
||||
`Subscribe to iCalendar file <schedule.ics>`_
|
||||
|
||||
Cross-project events
|
||||
====================
|
||||
|
||||
.. _c-vptg:
|
||||
|
||||
PTG (virtual)
|
||||
-------------
|
||||
|
||||
From October 23 to October 27 we'll have a virtual PTG to plan the Caracal
|
||||
release schedule.
|
||||
|
||||
.. _c-1:
|
||||
|
||||
Caracal-1 milestone
|
||||
-------------------
|
||||
|
||||
November 16, 2023 is the Caracal-1 milestone. See project-specific notes
|
||||
for relevant deadlines.
|
||||
|
||||
.. _c-cycle-trail:
|
||||
|
||||
Bobcat Cycle-Trailing Release Deadline
|
||||
--------------------------------------
|
||||
|
||||
All projects following the cycle-trailing release model must release
|
||||
their Bobcat deliverables by 7 December, 2023.
|
||||
|
||||
.. _c-2:
|
||||
|
||||
Caracal-2 milestone
|
||||
-------------------
|
||||
|
||||
January 11, 2024 is the Caracal-2 milestone. See project-specific notes
|
||||
for relevant deadlines.
|
||||
|
||||
.. _c-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.
|
||||
|
||||
.. _c-extra-atcs:
|
||||
|
||||
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 date.
|
||||
|
||||
.. _c-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.
|
||||
|
||||
.. _c-3:
|
||||
|
||||
Caracal-3 milestone
|
||||
-------------------
|
||||
|
||||
February 29, 2024 is the Caracal-3 milestone. See project-specific notes
|
||||
for relevant deadlines.
|
||||
|
||||
.. _c-ff:
|
||||
|
||||
Feature freeze
|
||||
--------------
|
||||
|
||||
The Caracal-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
|
||||
|
||||
.. _c-final-clientlib:
|
||||
|
||||
Final release for client libraries
|
||||
----------------------------------
|
||||
|
||||
Client libraries should issue their final release during this week, to match
|
||||
feature freeze.
|
||||
|
||||
.. _c-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).
|
||||
|
||||
.. _c-rf:
|
||||
|
||||
Requirements freeze
|
||||
-------------------
|
||||
|
||||
After the Caracal-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.
|
||||
|
||||
.. _c-rc1:
|
||||
|
||||
RC1 target week
|
||||
---------------
|
||||
|
||||
The week of March 11, 2023 is the target date for projects following the
|
||||
`release:cycle-with-rc`_ model to issue their first release candidate.
|
||||
|
||||
.. _c-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.
|
||||
|
||||
.. _c-finalrc:
|
||||
|
||||
Final RCs and intermediary releases
|
||||
-----------------------------------
|
||||
|
||||
The week of March 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).
|
||||
|
||||
.. _c-final:
|
||||
|
||||
Caracal release
|
||||
---------------
|
||||
|
||||
The Caracal coordinated release will happen on Wednesday, April 3, 2023.
|
||||
|
||||
.. _c-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
|
||||
=======================
|
||||
|
113
doc/source/caracal/schedule.yaml
Normal file
113
doc/source/caracal/schedule.yaml
Normal file
@ -0,0 +1,113 @@
|
||||
---
|
||||
start-week: 2023-10-09
|
||||
release-week: 2024-04-01
|
||||
cycle:
|
||||
- end: '2023-10-06'
|
||||
start: '2023-10-02'
|
||||
x-project:
|
||||
- b-final
|
||||
- end: '2023-10-13'
|
||||
name: R-25
|
||||
start: '2023-10-09'
|
||||
- end: '2023-10-20'
|
||||
name: R-24
|
||||
start: '2023-10-16'
|
||||
- end: '2023-10-27'
|
||||
name: R-23
|
||||
start: '2023-10-23'
|
||||
x-project:
|
||||
- c-vptg
|
||||
- end: '2023-11-03'
|
||||
name: R-22
|
||||
start: '2023-10-30'
|
||||
- end: '2023-11-10'
|
||||
name: R-21
|
||||
start: '2023-11-06'
|
||||
- end: '2023-11-17'
|
||||
name: R-20
|
||||
start: '2023-11-13'
|
||||
x-project:
|
||||
- c-1
|
||||
- end: '2023-11-24'
|
||||
name: R-19
|
||||
start: '2023-11-20'
|
||||
- end: '2023-12-01'
|
||||
name: R-18
|
||||
start: '2023-11-27'
|
||||
- end: '2023-12-08'
|
||||
name: R-17
|
||||
start: '2023-12-04'
|
||||
x-project:
|
||||
- c-cycle-trail
|
||||
- end: '2023-12-15'
|
||||
name: R-16
|
||||
start: '2023-12-11'
|
||||
- end: '2023-12-22'
|
||||
name: R-15
|
||||
start: '2023-12-18'
|
||||
- end: '2023-12-29'
|
||||
name: R-14
|
||||
start: '2023-12-25'
|
||||
- end: '2024-01-05'
|
||||
name: R-13
|
||||
start: '2024-01-01'
|
||||
- end: '2024-01-12'
|
||||
name: R-12
|
||||
start: '2024-01-08'
|
||||
x-project:
|
||||
- c-2
|
||||
- c-mf
|
||||
- end: '2024-01-19'
|
||||
name: R-11
|
||||
start: '2024-01-15'
|
||||
- end: '2024-01-26'
|
||||
name: R-10
|
||||
start: '2024-01-22'
|
||||
- end: '2024-02-02'
|
||||
name: R-9
|
||||
start: '2024-01-29'
|
||||
- end: '2024-02-09'
|
||||
name: R-8
|
||||
start: '2024-02-05'
|
||||
- end: '2024-02-16'
|
||||
name: R-7
|
||||
start: '2024-02-12'
|
||||
x-project:
|
||||
- c-extra-atcs
|
||||
- end: '2024-02-23'
|
||||
name: R-6
|
||||
start: '2024-02-19'
|
||||
x-project:
|
||||
- c-final-lib
|
||||
- end: '2024-03-01'
|
||||
name: R-5
|
||||
start: '2024-02-26'
|
||||
x-project:
|
||||
- c-3
|
||||
- c-ff
|
||||
- c-final-clientlib
|
||||
- c-soft-sf
|
||||
- c-rf
|
||||
- c-cycle-highlights
|
||||
- end: '2024-03-08'
|
||||
name: R-4
|
||||
start: '2024-03-04'
|
||||
- end: '2024-03-15'
|
||||
name: R-3
|
||||
start: '2024-03-11'
|
||||
x-project:
|
||||
- c-rc1
|
||||
- c-hard-sf
|
||||
- end: '2024-03-22'
|
||||
name: R-2
|
||||
start: '2024-03-18'
|
||||
- end: '2024-03-29'
|
||||
name: R-1
|
||||
start: '2024-03-25'
|
||||
x-project:
|
||||
- c-finalrc
|
||||
- end: '2024-04-05'
|
||||
name: R+0
|
||||
start: '2024-04-01'
|
||||
x-project:
|
||||
- c-final
|
@ -22,6 +22,7 @@ updates.
|
||||
:maxdepth: 1
|
||||
:hidden:
|
||||
|
||||
caracal/index
|
||||
bobcat/index
|
||||
antelope/index
|
||||
zed/index
|
||||
|
Loading…
Reference in New Issue
Block a user