openstack
/
project-team-guide
Code Issues Proposed changes

Revise the tick deprecation example 

As discussed in the PTG, the tick deprecation example was too
aggressive in its requirements for notice, requiring more notice
time than we require today. This was not the intent, so this corrects
that to the expected timeline.

Change-Id: I241cf3723312b299697a44ee43cc8aeadfadadd7
This commit is contained in:
Dan Smith 2022-04-12 11:52:56 -07:00
parent ef313d1f8e
commit b6b26faefe
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/source/deprecation.rst
View File

@ -59,13 +59,13 @@ or operator-visible features deprecation:
release branch, and for at least 12 months of releases. Consider
the following examples:
#. A feature deprecated in the 2023 tick release should still
appear (deprecated, but supported) in the 2023 tock release, and
may be removed in the 2024 tick release. Operators deploying
only tick releases receive one notice and have 12 months before
the next tick where the feature is removed. Operators deploying
tick-tock releases receive two notices and still have 12 months
before the release where the feature is removed.
#. A feature deprecated in the 2023 tick release may be removed in
the 2023 tock release. Operators deploying only tick releases
receive one notice and have 12 months before the next tick where
the feature is removed. Operators deploying tick-tock releases
receive one notice and have 6 months before the release where
the feature is removed, as was the case before the tick-tock
model.
#. A feature deprecated in the 2023 tock release must also be
present and supported the 2024 tick release, and **must** also