-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Releasing, Versioning and Deprecation #582
Comments
bot_skip |
We did a maintenance release this morning, 0.2.1, which is 0.2.0 with all references to the We recently also did a 0.3.0-experimental.meta.redirects release, which was taken from |
The 1.0.0 release will be on Friday, July 31st. |
Version 1.0.0 has been released. From now on, bugfixes and new features that are merged need to be backported to the The 1.1.0 release is regularly scheduled for end of September. Since the Ansible 2.10.0 beta freeze is on 2020-08-14, we might release 1.1.0 already then. |
It was decided at the community meeting to do the 1.1.0 release on 2020-08-18 (Ansible 2.10 beta freeze). |
Version |
Version 1.2.0 will be released on 2020-09-30, i.e. next week Wednesday. |
Version 1.2.0 has been released. Next release will be 1.3.0 at ~end of November. |
I plan to release 1.3.0 in four days (Thursday, November 26th). |
1.3.0 has been released. The next 1.x.y release will be 1.3.1, whenever there is sufficient content. The next version including new features will be 2.0.0, planned for end of January 2021. |
We decided at the community meeting that patch releases (1.3.x) will be made roughly every three weeks, resp. shortly before Ansible 2.10.x releases. Assuming there are bugfixes to release, of course. This rythm might change in February 2021 when Ansible 3.0.0 is released (with community.general 2.0.0). |
1.3.1 will be released on December 21th (i.e. tomorrow). |
1.3.1 has been released. 1.3.2 might be released at the beginning of January, before Ansible 2.10.5 is released, if we have any new bugfixes by then. |
1.3.2 has been released now. The next bugfix release 1.3.3 will probably be in three weeks, i.e. similar to when 2.0.0 will be released. |
1.3.3 has been released, addressing CVE-2021-20178. 1.3.4 will be released in ~two weeks, i.e. as planned for 1.3.3 before. |
1.3.4 has been released, addressing CVE-2021-20180. 1.3.5 will be released in ~two weeks, i.e. as planned for 1.3.3/1.3.4 before. |
Please note that there is a community vote on a new policy for which ansible-core versions to no longer support for a new community.general major release:
If you want to participate in that vote, please write a comment with |
6.6.5 and 7.4.0 have been released with bugfixes and the latter with new features. The next 7.x.y release is expected to be 7.5.0 in four weeks, which will be the last 7.x.0 minor release. 8.0.0 will likely be released at the end of October, in the week before November 6th, which happens to be feature freeze for Ansible 9 (see the Ansible 9 release schedule). |
Since the vote was accepted, I've added
as a new section "Ansible-core result" to the issue (#582 (comment)). #7259 has been merged to announce the deprecation, and a later PR (edit: #7269) will drop support for ansible-core 2.11 and 2.12 for the upcoming community.general 8.0.0 release. |
6.6.6 has been released with new bugfixes. The 7.5.0 release will follow tomorrow. |
7.5.0 has been released. The next 7.x.y release will be 7.5.1, in roughly four weeks. Note that the next minor or major release will be 8.0.0 in the week before November 6th. (Update: 7.5.0 is now really out. See edit history for details why this update is here.) |
8.0.0 has been released. There might be a 8.0.1 bugfix release in the next week or the week thereafter for Ansible 9.0.0b1 / Ansible 9.0.0rc1. |
5.8.10 has been released. This was the final 5.x.y release, the 5.x.y release train is now End of Life. |
6.6.7 has been released. This is the last regular 6.x.y bugfix release; from now on 6.x.y will only receive major bugfixes and security fixes, until it will be EOL in roughly 6 months when community.general 9.0.0 will be released. |
7.5.1 and 8.0.1 have been released. The next expected 7.x.y release will be 7.5.2 on December 4th, and the next expected 8.x.y release will be either 8.0.2 if a further bugfix release is needed for Ansible 9.0.0rc1 or a possible rc2, or 8.1.0 (also December 4th) for Ansible 9.1.0. |
8.0.2 has been released for inclusion in Ansible 9.0.0rc1. In case a second release candidate will be necessary for Ansible 9.0.0, a 8.0.3 release might be made, but for now I'm assuming the next 8.x.y release will be 8.1.0. |
7.5.2 has been released. The next 7.x.y release will be 7.5.3, released probably around January 1st. |
8.1.0 has been released. The next 8.x.y release will probably be 8.2.0, released around January 1st. |
8.2.0 and 7.5.3 have been released. The next 8.x.y release will probably be 8.3.0, and the next 7.x.y relesae will be 7.5.4, probably both released around January 29th. |
8.3.0 and 7.5.4 have been released. The next 8.x.y release will probably be 8.4.0, and the next 7.x.y release will be 7.5.5, probably both released around February 26th. |
7.5.5 has been released. The next expected 7.5.x release will be 7.5.6, probably around March 25th. |
8.4.0 has been released. The next expeted 8.x.y release will be 8.5.0 around March 25th. |
6.6.8 has been released with bugfixes and some security fixes. 7.5.6 and 8.5.0 will follow later today. |
7.5.6 and 8.5.0 have been released with new features (8.5.0 only), bugfixes, and some security fixes. The next expected releases are 8.6.0 and potentially 7.5.7 in four weeks. |
7.5.7 and 8.6.0 have been released with new features and modules (8.6.0 only) and bugfixes (both). The next expected releases for these release streams are 6.6.9, 7.5.8, 8.6.1 in four weeks. Please note that 8.6.0 will be the last 8.x.0 minor release. The next major release, 9.0.0, will happen in four weeks for inclusion in Ansible 10.0.0b1 (https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_10.html#release-schedule), in time for Ansible 10's feature freeze. Please note that at the same time, 6.6.9 will be the last 6.x.y release. The 6.x.y release stream will be End of Life from that point on. |
6.6.9 has been released. This is the last 6.x.y release. The 6.x.y release train is therefore End of Life. Thanks to everyone who contributed to it and worked on it! |
7.5.8 and 8.6.1 have been released. From now on, 7.5.x release will only come with security fixes and major bugfixes, and no more regular bugfixes. The 9.0.0 release will follow later today. |
9.0.0 has been released 🎉 The next 9.x.y release will be either 9.0.1 around May 27th, for inclusion in Ansible 10.0.0rc1, or 9.1.0 around June 17th, for inclusion in Ansible 10.1.0. |
9.0.1 is out with a few bugfixes for inclusion in Ansible 10.0.0rc1. If there is another Ansible 10 release candidate, we might have a 9.0.2 release in a week. Otherwise, the next 9.x.y release will likely be 9.1.0 around June 17th for Ansible 10.1.0. |
9.1.0 and 8.6.2 have been released with bugfixes and new features (for 9.1.0). The next expected releases will be around July 15th, potentially also 1-2 days earlier. |
8.6.3 has been released with bugfixes. The next expected 8.x.y release (8.6.4) will be around August 12th. |
9.2.0 has been released with bugfixes and new features. The next expected release (9.3.0) will be around September 15th. |
8.6.4 has been released with bugfixes. The next expected 8.x.y release (8.6.5) will be around September 9th. |
9.3.0 has been released with new features and bugfixes. The next expected 9.x.y release is 9.4.0 around September 9th. |
8.6.5 has been released with new bugfixes. The next expected 8.x.y release (8.6.6) will be around October 7th. |
9.4.0 has been released with new features and bugfixes. The next expected 9.x.y release is 9.5.0 around October 7th. Note that this will likely be the last 9.x.y feature release, and 10.0.0 will be released roughly four weeks after 9.5.0 for Ansible 11.0.0's feature freeze (https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_11.html#release-schedule). |
Introduction
This issue describes how and when community.general is released, and to announce updates to the release/versioning schedule. The next section (Next release) is always updated to contain the next version to be released. Other changes to this first post are always announced by separate posts in this issue.
Next releases
10.0.0 around November 4th
9.4.0 around October 7th
8.6.6 around October 7th
7.5.9 when needed
Releasing schedule for major and minor versions
master
branch)From then on:
The precise dates will be announced on time. Before Ansible releases we might introduce additional minor releases to fix issues.
If no new commit has been merged for a minor release, it must be skipped. Major versions must not be skipped.
The schedule for minor versions might be adjusted in the future (maybe once per month, maybe something else). The release schedule for patch versions (see below) would be adjusted.
Releasing schedule for patch versions
x.y.z
until the last minor release of a major release branch will only be released when necessary. The intended frequency is never, they are reserved for packaging failures, or fixing major breakage / security problems.x.2.0
, generallyx.Y.0
) has been released, there will be bugfix releasesx.Y.z
.Versioning
galaxy.yml
in themaster
branch will always contain the version of the next major or minor release. It will be updated right after a release.version_added
needs to be used for every new feature and module/plugin, and needs to coincide with the next minor/major release version. (This will eventually be enforced by CI.)Branching
stable-x
branches.stable-x
is branched.stable-x
release branch afterx.0.0
, and until the last minor release forstable-x
has been released.stable-x
branches.main
branch, the three lateststable-x
branches receive backports.x.2.0
, maintainers can merge backports themselves via bot. The bot will hopefully also allow to create backports automatically (if possible without conflicts). (We hope that they know the rules: no breaking of backwards compatibility!)x.2.0
on, only RM will merge backports.Deprecation
Changelogs
trivial
category should then be used to document changes which are not important enough to end up in the text version of the changelog.)(x+1).0.0
changelog continues thex.0.0
changelog.x.y.0
changelog withy > 0
is not part of a changelog of a laterX.*.*
(withX > x
) orx,Y,*
(withY > y
) release.x.y.z
changelog withz > 0
is not part of a changelog of a later(x+1).*.*
orx.Y.z
(withY > y
) release.ancestor
feature (inchangelogs/changelog.yaml
) to point to the previous major release.Ansible-core support
For every new major release of community.general, the collection drops support for all ansible-core versions that have been End of Life for at least a couple of weeks before the release date.
The text was updated successfully, but these errors were encountered: