Skip to content
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) #64

Closed
felixfontein opened this issue Jun 14, 2020 · 4 comments
Closed

Information on next release (0.2.0) #64

felixfontein opened this issue Jun 14, 2020 · 4 comments

Comments

@felixfontein
Copy link
Collaborator

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 all version_added and deprecation version numbers are fixed (version_added was updated in #21, depecations will be updated in #63). The 0.1.0 release is not counted as a proper release, it was 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 to 1.0.0. (There is unfortunately not yet a sanity check for this like there used to be in ansible/ansible.)

bot_skip

@felixfontein felixfontein pinned this issue Jun 14, 2020
@felixfontein
Copy link
Collaborator Author

The release is essentially done, except that the upload step wasn't set up. So the actual release will show up during the next days.

@felixfontein
Copy link
Collaborator Author

@gundalow will build and upload the collection on Monday.

@felixfontein
Copy link
Collaborator Author

0.2.0 has been published to Galaxy!

@felixfontein
Copy link
Collaborator Author

See #81 about information on the next releases.

@felixfontein felixfontein unpinned this issue Jun 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant