ansible-base 2.10 release happening soon. We'll
have changelogs and porting guides for that(samccann,
14:43:43)
we will update the `latest` symlink for the
docs only after ansible 2.10 is released(acozine,
14:43:47)
but we won't switch the version switcher to
include 2.10, or change the pages that /latest/ refers to until
Ansible releases later(samccann,
14:43:54)
Thursday's release of ansible-base should not
change the /latest/ url to 2.10 (it should stay 2.9) - if you see
problems, please let us know here in irc(samccann,
14:52:30)
AGREED: - separate
ansible-base from Ansible on the release-maintenance page,
preferably before Thurs(samccann,
15:11:48)
ACTION: samccann to
ask tower folks how they ensured people always looked at the newest
version of that release page(samccann,
15:13:11)
ACTION: samccann to
create a quick PR to make the release/maintenance page have separate
sections for ansible-base vs ansible(samccann,
15:14:21)
updates on porting guide, changelogs, and pipeline(acozine, 15:17:09)
some collections are converting their
changelogs to use our tool. We have one request so far for a direct
link to a collections changelog due to format requirements unique to
that community.(samccann,
15:21:09)
pipeline redirects work starting. We will open
an issue 'someplace logical' to explain the strategy of the
redirects(samccann,
15:21:51)
this would redirect someone who had a bookmark
to /latest/some-module so it goes to
/latest/collections/blabla/some-module... and the reverse.. so to
speak. See issue when it is created for more details(samccann,
15:22:45)
ACTION: samccann to
create a tracking issue for the redirects(samccann,
15:23:03)
check
https://github.com/ansible/ansible/projects/27#column-2809177 for
list of priority items we are tracking for Ansible 2.10 release. Let
us know if you see something else we need to track(samccann,
15:30:51)