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
As Ansible 11 was released and included kubernetes.core collections 5.0.0 means that branch stable-5 become the default one for the most of users who install ansible comunity package as pip install ansible, and documentation from the branch stable-5 (more specifically, to the released versions 5.x.y from that branch) appeared in the ansible documentation site.
However, since Jun 10 when 5.0.0 was released, we have had a lot of smaller and bigger changes that are not included in any released version of the collection kubernetes.core, and some of them have even not been cherry-picked to the stable-5 branch, which led, for the example that ansible galaxy contains deprecated communication channels.
So, it's time to release a new release from the branch stable-5 (that should be 5.1.0) and, probably stable-3 (that should be 3.2.0 in this case) but it's less important.
SUMMARY
Release a new version 5.1.0
To do that, some PRs that weren't cherry-picked to stable-5 should be merged in that branch (label backport-5 to be added):
The listed PRs are merged to main but don't have the label backport-5 and are missed in branch stable-5.
It will be nice to add, on the top of above, PRs that is a fully ready, and passed CI testing, so, it will be nice to review and merge (with backport-5 label) following PRs:
Other PRs should be checked as they were relatively old.
Maintainers can consider releases from both, stable-3 and stable-5 branches, in this case, it's better to have 3.3.0 and then 5.1.0, but I don't see a reason for release 3.3.0 as ansible-core versions 2.14 and 2.15 is not maintained anymore. However, the previous release of Ansible community package (Ansible 10) included 3.x.y version of the collection which meant that the release branch stable-3 should be kept maintained.
ISSUE TYPE
Feature Idea
COMPONENT NAME
kubernetes.core
ADDITIONAL INFORMATION
I can help with PR for the release (similar to #746), but I haven't rights to place labels (which means that I can't trigger CI job for cherry-pic), and action from maintainers is required.
The text was updated successfully, but these errors were encountered:
As Ansible 11 was released and included kubernetes.core collections 5.0.0 means that branch
stable-5
become the default one for the most of users who install ansible comunity package aspip install ansible
, and documentation from the branch stable-5 (more specifically, to the released versions 5.x.y from that branch) appeared in the ansible documentation site.However, since Jun 10 when 5.0.0 was released, we have had a lot of smaller and bigger changes that are not included in any released version of the collection kubernetes.core, and some of them have even not been cherry-picked to the
stable-5
branch, which led, for the example that ansible galaxy contains deprecated communication channels.So, it's time to release a new release from the branch
stable-5
(that should be 5.1.0) and, probably stable-3 (that should be 3.2.0 in this case) but it's less important.SUMMARY
Release a new version 5.1.0
To do that, some PRs that weren't cherry-picked to
stable-5
should be merged in that branch (label backport-5 to be added):The listed PRs are merged to
main
but don't have the labelbackport-5
and are missed in branchstable-5
.It will be nice to add, on the top of above, PRs that is a fully ready, and passed CI testing, so, it will be nice to review and merge (with
backport-5
label) following PRs:Other PRs should be checked as they were relatively old.
Maintainers can consider releases from both,
stable-3
andstable-5
branches, in this case, it's better to have 3.3.0 and then 5.1.0, but I don't see a reason for release 3.3.0 as ansible-core versions 2.14 and 2.15 is not maintained anymore. However, the previous release of Ansible community package (Ansible 10) included 3.x.y version of the collection which meant that the release branchstable-3
should be kept maintained.ISSUE TYPE
COMPONENT NAME
kubernetes.core
ADDITIONAL INFORMATION
I can help with PR for the release (similar to #746), but I haven't rights to place labels (which means that I can't trigger CI job for cherry-pic), and action from maintainers is required.
The text was updated successfully, but these errors were encountered: