wbrawner/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ansible/docs/docsite/rst/reference_appendices/release_and_maintenance.rst

149 lines
6.3 KiB
ReStructuredText
Raw Normal View History

Improve release and development cycle documentation This commit: - Adds a table highlighting the status of each version and provides a link to each major release's changelog - Re-inforces how stable versions are maintained and for how long - Moves this documentation out of the developer tree (this is interesting for users too!) while keeping a link there.
2017-07-21 20:05:02 +00:00
Release and maintenance
=======================
.. contents:: Topics
:local:
Clarify the release and maintenance cycle (#32402) * Clarify the release and maintenance cycle * Namespace refs a little * Fix an unrelated problem with plugin return docs to fix docs build
2017-11-01 05:08:14 +00:00
.. _release_cycle:
Improve release and development cycle documentation This commit: - Adds a table highlighting the status of each version and provides a link to each major release's changelog - Re-inforces how stable versions are maintained and for how long - Moves this documentation out of the developer tree (this is interesting for users too!) while keeping a link there.
2017-07-21 20:05:02 +00:00
Release cycle
`````````````
Ansible is developed and released on a flexible 4 months release cycle.
This cycle can be extended in order to allow for larger changes to be properly
implemented and tested before a new release is made available.
Clarify the release and maintenance cycle (#32402) * Clarify the release and maintenance cycle * Namespace refs a little * Fix an unrelated problem with plugin return docs to fix docs build
2017-11-01 05:08:14 +00:00
Ansible has a graduated support structure that extends to three major releases.
For more information, read about the `development and stable version maintenance workflow`_ or see
the chart in :ref:`schedule` for the degrees to which current releases are supported.
.. note:: Support for three major releases began with Ansible-2.4. Ansible-2.3 and older versions
are only supported for two releases.
Improve release and development cycle documentation This commit: - Adds a table highlighting the status of each version and provides a link to each major release's changelog - Re-inforces how stable versions are maintained and for how long - Moves this documentation out of the developer tree (this is interesting for users too!) while keeping a link there.
2017-07-21 20:05:02 +00:00
If you are using a release of Ansible that is no longer supported, we strongly
encourage you to upgrade as soon as possible in order to benefit from the
latest features and security fixes.
Clarify the release and maintenance cycle (#32402) * Clarify the release and maintenance cycle * Namespace refs a little * Fix an unrelated problem with plugin return docs to fix docs build
2017-11-01 05:08:14 +00:00
Older, unsupported versions of Ansible can contain unfixed security
Improve release and development cycle documentation This commit: - Adds a table highlighting the status of each version and provides a link to each major release's changelog - Re-inforces how stable versions are maintained and for how long - Moves this documentation out of the developer tree (this is interesting for users too!) while keeping a link there.
2017-07-21 20:05:02 +00:00
vulnerabilities (*CVE*).
Link to all the porting guides instead of just the 2.0 one (#30671)
2017-09-21 10:32:13 +00:00
You can refer to the `porting guides`_ for tips on updating your Ansible
Improve release and development cycle documentation This commit: - Adds a table highlighting the status of each version and provides a link to each major release's changelog - Re-inforces how stable versions are maintained and for how long - Moves this documentation out of the developer tree (this is interesting for users too!) while keeping a link there.
2017-07-21 20:05:02 +00:00
playbooks to run on newer versions.
Link to all the porting guides instead of just the 2.0 one (#30671)
2017-09-21 10:32:13 +00:00
.. _porting guides: https://docs.ansible.com/ansible/porting_guides.html
Improve release and development cycle documentation This commit: - Adds a table highlighting the status of each version and provides a link to each major release's changelog - Re-inforces how stable versions are maintained and for how long - Moves this documentation out of the developer tree (this is interesting for users too!) while keeping a link there.
2017-07-21 20:05:02 +00:00
Clarify the release and maintenance cycle (#32402) * Clarify the release and maintenance cycle * Namespace refs a little * Fix an unrelated problem with plugin return docs to fix docs build
2017-11-01 05:08:14 +00:00
.. _release_schedule:
Improve release and development cycle documentation This commit: - Adds a table highlighting the status of each version and provides a link to each major release's changelog - Re-inforces how stable versions are maintained and for how long - Moves this documentation out of the developer tree (this is interesting for users too!) while keeping a link there.
2017-07-21 20:05:02 +00:00
Release status
``````````````
Clarify the release and maintenance cycle (#32402) * Clarify the release and maintenance cycle * Namespace refs a little * Fix an unrelated problem with plugin return docs to fix docs build
2017-11-01 05:08:14 +00:00
=============== ========================== =================================================
Ansible Release Latest Version Status
=============== ========================== =================================================
devel `2.5`_ (unreleased, trunk) In development
Update the release doc with ansible-2.4.3
2018-01-31 20:30:11 +00:00
2.4 `2.4.3`_ (2018-01-31) Supported (security **and** general bug fixes)
Clarify the release and maintenance cycle (#32402) * Clarify the release and maintenance cycle * Namespace refs a little * Fix an unrelated problem with plugin return docs to fix docs build
2017-11-01 05:08:14 +00:00
2.3 `2.3.2`_ (2017-08-08) Supported (security **and** critical bug fixes)
2.2 `2.2.3`_ (2017-05-09) Unsupported (end of life)
2.1 `2.1.6`_ (2017-06-01) Unsupported (end of life)
2.0 `2.0.2`_ (2016-04-19) Unsupported (end of life)
1.9 `1.9.6`_ (2016-04-15) Unsupported (end of life)
<1.9 n/a Unsupported (end of life)
=============== ========================== =================================================
.. note:: Starting with Ansible-2.4, support lasts for 3 releases. Thus Ansible-2.4 will receive
security and general bug fixes when it is first released, security and critical bug fixes when
2.5 is released, and **only** security fixes once 2.6 is released.
Improve release and development cycle documentation This commit: - Adds a table highlighting the status of each version and provides a link to each major release's changelog - Re-inforces how stable versions are maintained and for how long - Moves this documentation out of the developer tree (this is interesting for users too!) while keeping a link there.
2017-07-21 20:05:02 +00:00
Updated release table for docs (#30649) - Updated table to reflect release of 2.4 - Added in 2.5 as current devel
2017-09-20 20:58:21 +00:00
.. _2.5: https://github.com/ansible/ansible/blob/devel/CHANGELOG.md
Update the release doc with ansible-2.4.3
2018-01-31 20:30:11 +00:00
.. _2.4.3: https://github.com/ansible/ansible/blob/stable-2.4/CHANGELOG.md
Update release status for 2.3 to 2.3.2
2017-08-11 19:29:28 +00:00
.. _2.3.2: https://github.com/ansible/ansible/blob/stable-2.3/CHANGELOG.md
Improve release and development cycle documentation This commit: - Adds a table highlighting the status of each version and provides a link to each major release's changelog - Re-inforces how stable versions are maintained and for how long - Moves this documentation out of the developer tree (this is interesting for users too!) while keeping a link there.
2017-07-21 20:05:02 +00:00
.. _2.2.3: https://github.com/ansible/ansible/blob/stable-2.2/CHANGELOG.md
.. _2.1.6: https://github.com/ansible/ansible/blob/stable-2.1/CHANGELOG.md
.. _2.0.2: https://github.com/ansible/ansible/blob/stable-2.0/CHANGELOG.md
.. _1.9.6: https://github.com/ansible/ansible/blob/stable-1.9/CHANGELOG.md
.. _support_life:
.. _methods:
Clarify the release and maintenance cycle (#32402) * Clarify the release and maintenance cycle * Namespace refs a little * Fix an unrelated problem with plugin return docs to fix docs build
2017-11-01 05:08:14 +00:00
Improve release and development cycle documentation This commit: - Adds a table highlighting the status of each version and provides a link to each major release's changelog - Re-inforces how stable versions are maintained and for how long - Moves this documentation out of the developer tree (this is interesting for users too!) while keeping a link there.
2017-07-21 20:05:02 +00:00
Development and stable version maintenance workflow
```````````````````````````````````````````````````
The Ansible community develops and maintains Ansible on GitHub_.
Clarify the release and maintenance cycle (#32402) * Clarify the release and maintenance cycle * Namespace refs a little * Fix an unrelated problem with plugin return docs to fix docs build
2017-11-01 05:08:14 +00:00
New modules, plugins, features and bugfixes will always be integrated in what will become the next
major version of Ansible. This work is tracked on the ``devel`` git branch.
Improve release and development cycle documentation This commit: - Adds a table highlighting the status of each version and provides a link to each major release's changelog - Re-inforces how stable versions are maintained and for how long - Moves this documentation out of the developer tree (this is interesting for users too!) while keeping a link there.
2017-07-21 20:05:02 +00:00
Clarify the release and maintenance cycle (#32402) * Clarify the release and maintenance cycle * Namespace refs a little * Fix an unrelated problem with plugin return docs to fix docs build
2017-11-01 05:08:14 +00:00
Ansible provides bugfixes and security improvements for the most recent major release. The previous
major release will only receive fixes for security issues and critical bugs. Ansible only applies
security fixes to releases which are two releases old. This work is tracked on the
``stable-<version>`` git branches.
.. note:: Support for three major releases began with Ansible-2.4. Ansible-2.3 and older versions
are only supported for two releases with the first stage including both security and general bug
fixes while the second stage includes security and critical bug fixes
Improve release and development cycle documentation This commit: - Adds a table highlighting the status of each version and provides a link to each major release's changelog - Re-inforces how stable versions are maintained and for how long - Moves this documentation out of the developer tree (this is interesting for users too!) while keeping a link there.
2017-07-21 20:05:02 +00:00
The fixes that land in supported stable branches will eventually be released
as a new version when necessary.
For more information on the changes included in each new version, you can refer
to the changelog_, available on GitHub.
Note that while there are no guarantees for providing fixes for unsupported
releases of Ansible, there can sometimes be exceptions for critical issues.
.. _GitHub: https://github.com/ansible/ansible
.. _changelog: https://github.com/ansible/ansible/blob/devel/CHANGELOG.md
Clarify the release and maintenance cycle (#32402) * Clarify the release and maintenance cycle * Namespace refs a little * Fix an unrelated problem with plugin return docs to fix docs build
2017-11-01 05:08:14 +00:00
Improve release and development cycle documentation This commit: - Adds a table highlighting the status of each version and provides a link to each major release's changelog - Re-inforces how stable versions are maintained and for how long - Moves this documentation out of the developer tree (this is interesting for users too!) while keeping a link there.
2017-07-21 20:05:02 +00:00
Release candidates
~~~~~~~~~~~~~~~~~~
Before a new release or version of Ansible can be done, it will typically go
through a release candidate process.
This provides the Ansible community the opportunity to test Ansible and report
bugs or issues they might come across.
Ansible tags the first release candidate (``RC1``) which is usually scheduled
to last five business days. The final release is done if no major bugs or
issues are identified during this period.
If there are major problems with the first candidate, a second candidate will
be tagged (``RC2``) once the necessary fixes have landed.
This second candidate lasts for a shorter duration than the first.
If no problems have been reported after two business days, the final release is
done.
More release candidates can be tagged as required, so long as there are
bugs that the Ansible core maintainers consider should be fixed before the
final release.
Clarify the release and maintenance cycle (#32402) * Clarify the release and maintenance cycle * Namespace refs a little * Fix an unrelated problem with plugin return docs to fix docs build
2017-11-01 05:08:14 +00:00
.. _release_freezing:
Improve release and development cycle documentation This commit: - Adds a table highlighting the status of each version and provides a link to each major release's changelog - Re-inforces how stable versions are maintained and for how long - Moves this documentation out of the developer tree (this is interesting for users too!) while keeping a link there.
2017-07-21 20:05:02 +00:00
Feature freeze
~~~~~~~~~~~~~~
While there is a pending release candidate, the focus of core developers and
maintainers will on fixes towards the release candidate.
Merging new features or fixes that are not related to the release candidate may
be delayed in order to allow the new release to be shipped as soon as possible.
.. seealso::
:doc:`committer_guidelines`
Guidelines for Ansible core contributors and maintainers
:doc:`test_strategies`
Testing strategies
:doc:`community`
Community information and contributing
`Ansible Changelog <https://github.com/ansible/ansible/blob/devel/CHANGELOG.md>`_
Documentation of the improvements for each version of Ansible
`Ansible release tarballs <https://releases.ansible.com/ansible/>`_
Ansible release tarballs
`Development Mailing List <http://groups.google.com/group/ansible-devel>`_
Mailing list for development topics
`irc.freenode.net <http://irc.freenode.net>`_
#ansible IRC chat channel
Reference in a new issue Copy permalink