ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

corrected section anchors

Browse source
This commit is contained in:
Brian Coca 2015-12-12 12:59:00 -05:00
parent 14f3739260
commit 8db2912745
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docsite/rst/developing_releases.rst
View file

@ -4,7 +4,7 @@ Releases
.. contents:: Topics .. contents:: Topics
:local: :local:
.. schedule:: .. _schedule:
Release Schedule Release Schedule
```````````````` ````````````````
@ -16,7 +16,7 @@ When a fix/feature gets added to the `devel` branch it will be part of the next
Sometimes an RC can be extended by a few days if a bugfix makes a change that can have far reaching consequences, so users have enough time to find any new issues that may stem from this. Sometimes an RC can be extended by a few days if a bugfix makes a change that can have far reaching consequences, so users have enough time to find any new issues that may stem from this.
.. methods:: .. _methods:
Release methods Release methods
```````````````` ````````````````
@ -25,7 +25,7 @@ Ansible normally goes through a 'release candidate', issuing an RC1 for a releas
Otherwise fixes will be applied and an RC2 will be provided for testing and if no bugs after 2 days, the final release will be made, iterating this last step and incrementing the candidate number as we find major bugs. Otherwise fixes will be applied and an RC2 will be provided for testing and if no bugs after 2 days, the final release will be made, iterating this last step and incrementing the candidate number as we find major bugs.
.. freezing:: .. _freezing:
Release feature freeze Release feature freeze
`````````````````````` ``````````````````````