Adjust Ansible 12 release schedule

Project Discussions
, ,
1

Now that there as been a first announcement on ansible-core 2.19’s delay (ansible-core 2.19 release schedule update), we should think about Ansible 12’s release schedule (Ansible project 12.0 — Ansible Community Documentation).

I think it would be best to simply adjust it so that it aligns with the new dates of ansible-core, i.e.:

  • ansible-core beta releases get a Ansible alpha release a day later;
  • ansible-core’s rc releases gets Ansible beta releases a day later;
  • and ansible-core 2.19.0 GA gets Ansible feature freeze a day later;
  • Ansible 12.0.0rc1 a week after that;
  • and 1-2 weeks later 12.0.0 comes out.

WDYT?

And how should we adjust the release schedule at Ansible project 12.0 — Ansible Community Documentation? Simply strike through the dates and add an info box that basically says the above (in nicer wording), and replace the dates once we have more exact ones for ansible-core?

3 Likes
2

As far as I can see, the ansible-core 2.19 roadmap hasn’t changed yet. I’m not sure if we should change any dates if we don’t have ones from core that we can point to.

Maybe start with an info box stating a delay because of and mentioning ansible-core 2.19 release schedule update?

At the very least, we should announce both here on the forum and on Bullhorn (maybe simply mentioning the forum post) that we will delay Ansible 12 because of the ansible-core 2.19 release schedule update.

3

That’s why I suggested to follow a generic pattern that is based on ansible-core pre-releases, instead of fixing dates :slight_smile:

Definitely!

4

I don’t have a better idea at the moment and this suggestion sounds good to me.

Additionally, how about documenting our usual approach (or a “general roadmap”) like in your list:

  • ansible-core beta releases get a Ansible alpha release a day later
  • ansible-core’s rc releases gets Ansible beta releases a day later

and so on in Ansible Roadmap?

5

I started drafting that: Describe general Ansible major version release schedule; announce that Ansible 12.0.0's release schedule gets delayed according to ansible-core 2.19.0's release schedule by felixfontein · Pull Request #2490 · ansible/ansible-documentation · GitHub

1 Like
6

I’ve commented. Anyone else from the @SteeringCommittee who might want to have a look?

7

As discussed on Wednesday I’ve repurposed that PR to only add a general release schedule, and removed the changes to the Ansible 12 release schedule.

The Ansible 12 release schedule got updated in Adjust Ansible 12 roadmap by felixfontein · Pull Request #2508 · ansible/ansible-documentation · GitHub after approval of 7 SC members. So this topic is basically done for now. Thanks everyone!

8

There’s a new delay: according to Core 2.19 beta extended thru June 30, ansible-core 2.19.0 GA will be released on July 21st, instead of June 16th. IMO we should adjust Ansible 12’s schedule once more to match ansible-core’s schedule.

1 Like
9

Yep, sorry we’re making life difficult there, but I know you understand it’s a lot easier to fine-tune these things before they’re shipped than after :laughing:

1 Like
10

I created a PR: Adjust Ansible 12's release schedule to ansible-core 2.19's updated schedule by felixfontein · Pull Request #2664 · ansible/ansible-documentation · GitHub
Since there’s no update yet for the ansible-core 2.19 roadmap, some dates I wasn’t able to fill in yet…

3 Likes
11

How should we proceed with the PR? (There’s still no PR for the ansible-core roadmap.) Should we wait for an update of the ansible-core roadmap, merge my PR as-is, …?

12

Since our Roadmap follows that of ansible-core, it would be really great if this would be updated first (hint hint @nitzmahone). Let’s give them a few more days to do it.

13

Sorry, been buried in, well, you know- I’ll try to have someone push a doc PR this morning or do it myself… Sivel usually handles the roadmap updates, but he’s been out for a few days.

The date shuffle we announced likely puts 2.19.0 on an off-cycle date with the other releases, but that’s OK- gives us a short cycle for 2.19.1, which history shows often ends up releasing early anyway.

In any case, the dates we announced are still good and should be reflected on the roadmap soon. Thanks!

1 Like
14
2 Likes
15

Thanks @nitzmahone, I’ve merged your PR. If nobody objects, I’ll merge my PR (adjusted with the dates as suggested by @mariolenz) soon as well.