-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Information on next release (0.2.0) #507
Comments
ansibullbot
added
affects_2.10
bug
This issue/PR relates to a bug
needs_info
This issue requires further information. Please answer any outstanding questions
needs_template
This issue/PR has an incomplete description. Please fill in the proposed template correctly
labels
Jun 14, 2020
bot_skip |
felixfontein
removed
affects_2.10
bug
This issue/PR relates to a bug
needs_info
This issue requires further information. Please answer any outstanding questions
needs_template
This issue/PR has an incomplete description. Please fill in the proposed template correctly
labels
Jun 14, 2020
0.2.0 has just been released. The next release will be 1.0.0; an announcement and information about 1.0.0 and later releases will follow soon. |
See #582 for information about the next releases. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We plan to release a first proper release of the community.general collection shortly, namely a "couple of days" after the initial ansible-base 2.10 beta is released. This is expected to happen during the next few days, i.e. 0.2.0 will probably be released this week.
This will be the first proper release in the sense that it will have a changelog which describes the changes to the modules and plugins in this collections since Ansible 2.9 beta 1 (i.e. when the
stable-2.9
branch was created in ansible/ansible), and that allversion_added
and deprecation version numbers are fixed (version_added
was updated in #214, depecations will be updated in #504). The 0.1.x releases are not counted as proper releases, they were mainly there so that the whole releasing process can be boot-strapped (it is not possible to upload collections with dependencies to Ansible Galaxy when the dependencies have never been released).The next release will be 1.0.0 (or a more precisely a pre-release for it), somewhen during the next months. (This will get pinned down more precisely soon.)
(In case you're interested in this process, everything was discussed and decided in the Ansible Community Working Group meetings, ansible/community#539. Next topics will be some details about community.general and community.network releasing, and defining the Ansible 2.10 release.)
Once all details for future releases of community.general and community.network are fixed, we will create another issue (pinned like this one) in this repository.
If you are creating PRs (or have PRs) which add new modules, plugins or features, these have to be documented with
version_added: 0.2.0
. If the PR didn't make it into 0.2.0, you need to increase the value to1.0.0
. (There is unfortunately not yet a sanity check for this like there used to be in ansible/ansible.)bot_skip
The text was updated successfully, but these errors were encountered: