On Tue, Jan 31, 2023 at 07:21:03PM -0700, Orion Poplawski wrote:
On 1/31/23 11:03, Maxwell G wrote:
> On Tue Jan 31, 2023 at 15:01 +0200, Sagi Shnaidman wrote:
> Hi all,
>
> > Hi, Orion
> > Thanks for raising this question.
>
> Indeed!
>
> > I wonder if it's possible to continue to update collections to the
> > newest versions anyway. If someone wants to use the collection version
> > provided in "big ansible", they would use ansible 6.3.0 with all
> > included. If they want a newer collection, they can install a separate
> > newest RPM.
>
> I agree. I think we should update collections to the next major version
> (if it exists) after each RHEL minor release and then keep them updated
> with point releases in between. We update the ansible bundle to the next
> major version that corresponds to RHEL's ansible-core version at each
> RHEL minor release, so it makes to do the same with the standalone
> collection packages. Collection versions that are EOL upstream won't be
> tested with newer ansible-core versions.
Does this capture the general sentiment?
- ansible is the static/stable collection of collections paired with the
provided ansible-core for the life of the point release
- ansible-collection-* packages will be at least the version of the
collection in ansible, and optionally higher while giving due diligence to
avoiding breaking changes.
That sounds mostly reasonable. I guess I could come up with a crazy case
like 'the version in ansible has some problem that wasn't noticed, so I
want to keep the seperate collection on a older version until it's
fixed' though.
kevin