summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBrian Coca <brian.coca+git@gmail.com>2015-12-27 14:17:20 -0500
committerBrian Coca <brian.coca+git@gmail.com>2015-12-27 14:17:58 -0500
commitb50ed10a840305edf0e7e0a74d29d40e17f3d5b8 (patch)
tree1746ffc4569c21bdffeea551b0da07e51cde87d9
parentb4fae25a96a8d61ac40a4be0ffd11a306ce14077 (diff)
downloadansible-b50ed10a840305edf0e7e0a74d29d40e17f3d5b8.tar.gz
updated release cycle to 4 months instead of 2
-rw-r--r--docsite/rst/intro_installation.rst9
1 files changed, 4 insertions, 5 deletions
diff --git a/docsite/rst/intro_installation.rst b/docsite/rst/intro_installation.rst
index e986ffd70f..a5ed83a302 100644
--- a/docsite/rst/intro_installation.rst
+++ b/docsite/rst/intro_installation.rst
@@ -27,12 +27,11 @@ What Version To Pick?
`````````````````````
Because it runs so easily from source and does not require any installation of software on remote
-machines, many users will actually track the development version.
+machines, many users will actually track the development version.
-Ansible's release cycles are usually about two months long. Due to this
-short release cycle, minor bugs will generally be fixed in the next release versus maintaining
-backports on the stable branch. Major bugs will still have maintenance releases when needed, though
-these are infrequent.
+Ansible's release cycles are usually about four months long. Due to this short release cycle,
+minor bugs will generally be fixed in the next release versus maintaining backports on the stable branch.
+Major bugs will still have maintenance releases when needed, though these are infrequent.
If you are wishing to run the latest released version of Ansible and you are running Red Hat Enterprise Linux (TM), CentOS, Fedora, Debian, or Ubuntu, we recommend using the OS package manager.