You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docsite/rst/roadmap/ansible_roadmap_index.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ The generic release schedule of a new major Ansible version ``X.0.0`` can be spl
40
40
41
41
1. If there have been release blockers, a second release candidate release, Ansible X.0.0 rc2, will happen on Tuesday of the following week (one week after X.0.0 rc1), and the general availability will usually happen one week after that (again on a Tuesday).
42
42
43
-
1. Four weeks after the ansible-core 2.Y.0 release, and 1-2 weeks after the Ansible X.0.0 release, ansible-core 2.Y.1 will be released on (usuaully) a Monday, and one day later (usually Tuesday) there will be the Ansible X.1.0 release.
43
+
1. Four weeks after the ansible-core 2.Y.0 release, and 1-2 weeks after the Ansible X.0.0 release, ansible-core 2.Y.1 will be released on (usually) a Monday, and one day later (usually Tuesday) there will be the Ansible X.1.0 release.
44
44
45
45
Note that the schedule might be extended with further Ansible X.0.0 beta or X.0.0 release candidate releases if circumstances require additional time, such as when larger changes in ansible-core require more testing in collections.
46
46
The above schedule (especially with X.0.0 being generally available one week after X.0.0 rc1) is an optimistic schedule, which usually works fine, but might not always provide enough time.
0 commit comments