Update ansible roadmap (#72838)
* Update to the ansible package roadmap for 3.0.0 * Rename files for the ansible roadmap from 2.11 to 3.0 Co-authored-by: Sandra McCann <samccann@redhat.com> Co-authored-by: Alicia Cozine <879121+acozine@users.noreply.github.com>
This commit is contained in:
Toshio Kuratomi
GitHub
parent
f569d80fde
commit
6608f3aab3
3 changed files with 46 additions and 43 deletions
|
|
@ -1,42 +0,0 @@
|
||||||
====================
|
|
||||||
Ansible project 2.11
|
|
||||||
====================
|
|
||||||
|
|
||||||
This release schedule includes dates for the `ansible <https://pypi.org/project/ansible/>`_ package, with a few dates for the `ansible-base <https://pypi.org/project/ansible-base/>`_ package as well. All dates are subject to change. See :ref:`base_roadmap_2_11` for the most recent updates on ``ansible-base``.
|
|
||||||
|
|
||||||
.. contents::
|
|
||||||
:local:
|
|
||||||
|
|
||||||
Release schedule
|
|
||||||
=================
|
|
||||||
|
|
||||||
.. note:: Dates subject to change.
|
|
||||||
|
|
||||||
- ????-??-?? Ansible 2.11 alpha freeze. No net new collections allowed after this date.
|
|
||||||
- ????-??-?? Ansible collections freeze date for content moving between collections.
|
|
||||||
- ????-??-?? Ansible 2.11 alpha.
|
|
||||||
- ????-??-?? Ansible 2.11.0 beta1 and feature freeze.
|
|
||||||
|
|
||||||
- No new modules or major features accepted after this date. In practice this means we will freeze the semver collection versions to compatible release versions. For example, if the version of community.crypto on this date was community-crypto-2.1.0; ansible-2.11.0 could ship with community-crypto-2.1.1. It would not ship with community-crypto-2.2.0.
|
|
||||||
|
|
||||||
- ????-??-?? Ansible 2.11 final freeze/rc1.
|
|
||||||
|
|
||||||
- After this date only changes blocking a release are accepted.
|
|
||||||
- Collections will only be updated to a new version if a blocker is approved. Collection owners should discuss any blockers at a community IRC meeting (before this freeze) to decide whether to bump the version of the collection for a fix. See the `Community IRC meeting agenda <https://github.com/ansible/community/issues/539>`_.
|
|
||||||
|
|
||||||
** Additional release candidates to be published as needed as blockers are fixed **
|
|
||||||
|
|
||||||
- ????-??-?? Ansible 2.11 GA release date.
|
|
||||||
|
|
||||||
.. note::
|
|
||||||
|
|
||||||
Breaking changes may be introduced in Ansible 2.11.0, although we encourage collection owners to use deprecation periods that will show up in at least one Ansible release before being changed incompatibly.
|
|
||||||
|
|
||||||
|
|
||||||
Ansible patch releases
|
|
||||||
=======================
|
|
||||||
|
|
||||||
Ansible 2.11.x patch releases will occur approximately every three weeks if changes to collections have been made or if it is deemed necessary to force an upgrade to a later ansible-base-2.11.x. Ansible 2.11.x patch releases may contain new features but not backwards incompatibilities. In practice, this means we will include new collection versions where either the patch or the minor version number has changed but not when the major number has changed. For example: if Ansible-2.11 ships with community-crypto-2.1.0; ansible-2.11.1 may ship with community-crypto-2.2.0 but would not ship with community-crypto-3.0.0).
|
|
||||||
|
|
||||||
|
|
||||||
For more information, reach out on a mailing list or an IRC channel - see :ref:`communication` for more details.
|
|
||||||
45
docs/docsite/rst/roadmap/COLLECTIONS_3_0.rst
Normal file
45
docs/docsite/rst/roadmap/COLLECTIONS_3_0.rst
Normal file
|
|
@ -0,0 +1,45 @@
|
||||||
|
===================
|
||||||
|
Ansible project 3.0
|
||||||
|
===================
|
||||||
|
|
||||||
|
This release schedule includes dates for the `ansible <https://pypi.org/project/ansible/>`_ package, with a few dates for the `ansible-base <https://pypi.org/project/ansible-base/>`_ package as well. All dates are subject to change. See :ref:`base_roadmap_2_11` for the most recent updates on ``ansible-base``.
|
||||||
|
|
||||||
|
.. contents::
|
||||||
|
:local:
|
||||||
|
|
||||||
|
Release schedule
|
||||||
|
=================
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
Ansible is switching from its traditional versioning scheme to `semantic versioning <https://semver.org/>`_ starting with this release. So this version is 3.0.0 instead of 2.11.0.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
:2020-12-16: Finalize rules for net-new collections submitted for the ansible release.
|
||||||
|
:2021-01-27: Final day for new collections to be **reviewed and approved**. They MUST be
|
||||||
|
submitted prior to this to give reviewers a chance to look them over and for collection owners
|
||||||
|
to fix any problems.
|
||||||
|
:2021-02-02: Ansible-3.0.0-beta1 -- feature freeze [1]_
|
||||||
|
:2021-02-09: Ansible-3.0.0-rc1 -- final freeze [2]_ [3]_
|
||||||
|
:2021-02-16: Release of Ansible-3.0.0
|
||||||
|
:2021-03-09: Release of Ansible-3.1.0 (bugfix + compatible features: every three weeks)
|
||||||
|
|
||||||
|
.. [1] No new modules or major features accepted after this date. In practice this means we will freeze the semver collection versions to compatible release versions. For example, if the version of community.crypto on this date was community-crypto-2.1.0; ansible-3.0.0 could ship with community-crypto-2.1.1. It would not ship with community-crypto-2.2.0.
|
||||||
|
|
||||||
|
.. [2] After this date only changes blocking a release are accepted. Accepted changes require creating a new rc and may slip the final release date.
|
||||||
|
.. [3] Collections will only be updated to a new version if a blocker is approved. Collection owners should discuss any blockers at a community IRC meeting (before this freeze) to decide whether to bump the version of the collection for a fix. See the `Community IRC meeting agenda <https://github.com/ansible/community/issues/539>`_.
|
||||||
|
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
Breaking changes may be introduced in Ansible 3.0.0, although we encourage collection owners to use deprecation periods that will show up in at least one Ansible release before the breaking change happens.
|
||||||
|
|
||||||
|
|
||||||
|
Ansible minor releases
|
||||||
|
=======================
|
||||||
|
|
||||||
|
Ansible 3.x.x minor releases will occur approximately every three weeks if changes to collections have been made or if it is deemed necessary to force an upgrade to a later ansible-base-2.10.x. Ansible 3.x.x minor releases may contain new features but not backwards incompatibilities. In practice, this means we will include new collection versions where either the patch or the minor version number has changed but not when the major number has changed. For example, if Ansible-3.0.0 ships with community-crypto-2.1.0; Ansible-3.1.0 may ship with community-crypto-2.2.0 but would not ship with community-crypto-3.0.0).
|
||||||
|
|
||||||
|
|
||||||
|
For more information, reach out on a mailing list or an IRC channel - see :ref:`communication` for more details.
|
||||||
|
|
@ -24,4 +24,4 @@ See :ref:`Ansible communication channels <communication>` for details on how to
|
||||||
:caption: Ansible Release Roadmaps
|
:caption: Ansible Release Roadmaps
|
||||||
|
|
||||||
COLLECTIONS_2_10
|
COLLECTIONS_2_10
|
||||||
COLLECTIONS_2_11
|
COLLECTIONS_3_0
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue