Release Planning Announcements

[felixfontein]

This continues #74. For policy discussion, see that issue. This issue is announce only, without discussions.

The next release will be 1.3.0 (tracked in #126).

[felixfontein]

1.3.0 has been released. The 1.4.0 release will be tracked in #148.

[felixfontein]

1.4.0 has been released. The 1.5.0 release will be tracked in #177.

[felixfontein]

1.5.0 has been released. The 1.6.0 release will be tracked in #194.

[felixfontein]

1.6.0 has been relesaed. The 1.7.0 release will be tracked in #209.

[felixfontein]

1.6.1 has been released on April 11 to fix #216.

[felixfontein]

1.6.2 has been released today to fix #220. The next planned release is still 1.7.0.

[felixfontein]

Looks like I forgot to update this, and only updated the per-release issues :)

1.8.0 tracking has been done in #244, 1.9.0 tracking is being done in #261, and 2.0.0 tracking is being done in #128.

[felixfontein]

1.9.3 has been released. 1.10.0 tracking is done in #266.

[felixfontein]

1.9.4 has been released. 1.10.0 is probably skipped (at least for now); the next expected release is 2.0.0 or some preview for it.

[felixfontein]

1.9.5 has been released. This is a compatibility release for cryptograph 35.0.0.

[felixfontein]

I'll release 1.9.6 later today (with a bugfix). The 2.0.0 release will also happen soon (see #128 for more updates on 2.0.0).

[felixfontein]

1.9.6 has been released with a bugfix.

[felixfontein]

2.0.0 has been released!

[felixfontein]

Since cryptography 36.0.0 will get released soon (this/next week), I plan to merge #302 and #331 once that happened (with tests re-run, and of course pending reviews) and create bugfix releases 2.0.1 / 1.9.7 with it.

[felixfontein]

It is somewhat likely that 36.0.0 will be released very soon (in the next ~13 hours, extrapolating from a similar answer on #pyca ~11 hours ago). Would be glad if someone could take a look at #331 so I can also merge it assuming CI still passes.

[felixfontein]

Since I don't know how much longer cryptography 36.0.0 will get delayed: I'll create a community.crypto bugfix release with the current set of merged bugfixes on Monday evening if 36.0.0 hasn't been released anyway, so they make it into Ansible 5.0.0rc1, which is to be released on Tuesday.

[felixfontein]

cryptography 36.0.0 has been released; I'll work on 2.0.1 and 1.9.7 releases later today.

[felixfontein]

1.9.7 and 2.0.1 have been released.

[felixfontein]

1.9.8 has been released with some documentation fixes.

[felixfontein]

2.0.2 has been released with some documentation fixes.

[felixfontein]

2.1.0 has been released! The next expected release, 2.2.0, is tracked in #375.

[felixfontein]

1.9.9 has been released with the bugfixes from 2.1.0 as well.

[felixfontein]

1.9.10 and 2.2.0 have been released. The next expected release is 2.3.0, which is tracked by a milestone and no longer a tracking issue. I hope that's ok for everyone (see also #24 (comment)).

[felixfontein]

1.9.11 and 2.2.1 have been released with a bugfix.

[felixfontein]

2.7.0 has been released with a new feature and improved compatibility with future ansible-core releases.

[felixfontein]

2.7.1 has been released with improved error reporting.

[felixfontein]

1.9.19 has been released with a bugfix. 2.8.0 will be released soon with new features.

[felixfontein]

2.8.0 is out with some new features.

[felixfontein]

2.8.1 has been released with updated docs.

[felixfontein]

2.9.0 has been released with a new feature.

[felixfontein]

1.9.20 has been released with a bugfix.

[felixfontein]

2.10.0 has been released with bugfixes and new filter plugins.

[felixfontein]

2.11.0 has been released with bugfixes and a new feature.

[felixfontein]

2.11.1 has been released with small docs fixes.

[felixfontein]

1.9.21 and 2.12.0 have ben released.

[felixfontein]

2.13.0 has been released with a bugfix and a maintenance update to work around a module option collision.

[felixfontein]

2.13.1 has been released with fixes to the EE binary dependencies.

[felixfontein]

1.9.22 has been released with a bugfix, and 2.14.0 has been released with some new features.

[felixfontein]

2.14.1 has been released and is now using semantic markup for documentation.

[felixfontein]

2.15.0 has been released with new features and bugfixes.

[felixfontein]

2.15.1 has been released with a bugfix in error handling for the ACME modules.

[felixfontein]

1.9.23 has been released with a bugfix. 2.16.0 has been released with a bugfix and new features for luks_device.

[felixfontein]

2.16.1 has been released with a bugfix.

[felixfontein]

2.16.2 has been released with some improvements to the ACME modules.

[felixfontein]

2.17.0 has been released with a new feature.

[felixfontein]

1.9.24 and 2.17.1 have been released with fixes that make them work with cryptography 24.0.0+.

[felixfontein]

2.18.0 has been released with new bugfixes, features, and a deprecation of the check mode behavior of the _pipe modules.

[felixfontein]

2.19.0 is out with bugfixes, new features, and a new module.

[felixfontein]

2.19.1 is out with bugfixes, in particular a fix that restores idempotency for x509_certificate (selfsigned and ownca providers) when notBefore or notAfter is used.

[felixfontein]

1.9.25 and 2.20.0 are out with bugfixes; 2.20.0 also has a new feature, three new ACME modules, and several deprecations for internal code and docs fragments, in case they are used by other collections.

[felixfontein]

2.21.0 is out with three new features.

[felixfontein]

2.21.1 is out to address a deprecation in cryptography 43.0.0.

[felixfontein]

community.crypto 1.x.y is now End of Life. There will be no further 1.x.y releases, and CI for stable-1 has been disabled.

Thanks to everyone who contributed to community.crypto 1.x.y!

[felixfontein]

2.22.0 is out with a new feature.