# \[Vote ended on 2023-12-04\] Release schedule for holiday releases

**URL:** <https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471>\
**Category:** Project Discussions\
**Tags:** implemented, release-management, community-wg\
**Created:** [November 20, 2023, 6:08pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471 "2023-11-20T18:08:37Z")\
**Posts on this page:** 13\
**Page:** 2

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [November 26, 2023, 6:34pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471/21 "2023-11-26T18:34:15Z")

</div>

I’ve proposed this over the weekend and wanted to give people more than just Monday to comment.

But since aligning more closely with ansible-core seems to be uncontroversial, I don’t have a problem with starting the vote tomorrow and ending it on December 4th.

That is, tomorrow afternoon or evening CET.

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [November 27, 2023, 3:31pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471/22 "2023-11-27T15:31:32Z")

</div>

Vote (ending **December 4th** ) on the following proposal:

1. Change the Ansible 9 roadmap (specifically: the timing of minor releases) as proposed in [Ansible 9: Follow ansible-core more closely](https://github.com/ansible/ansible-documentation/pull/856) so we do not have to discuss what to do every time when ansible-core delays a release.

2. Announce the change of our release policy on Bullhorn with:

> From now on, the Ansible community package release schedule will follow the Ansible Core release schedule, including (for example) delays for holidays. This means Ansible releases happen every four weeks through most of the year, but release dates may be delayed when Ansible Core release is.
> 
> For the upcoming holiday season, this means that there will be no Ansible release in early January, but instead on January 30th.

_Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471/22))_

_Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471/22))_

---

<div class="post-metadata">

**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\
**Post date:** [November 27, 2023, 4:07pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471/23 "2023-11-27T16:07:48Z")

</div>

> [@mariolenz](#):
>
> For the upcoming holiday season this

You’re missing a comma between `season` and `this`, but otherwise, this looks good to me 👍.

---

<div class="post-metadata">

**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\
**Post date:** [November 27, 2023, 4:08pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471/24 "2023-11-27T16:08:37Z")

</div>

Also, @mariolenz, I assume you want to vote on your own proposal 🙂.

---

<div class="post-metadata">

**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\
**Post date:** [November 27, 2023, 4:17pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471/25 "2023-11-27T16:17:24Z")

</div>

Since we’re starting to see more polls now, I’ll drop in a link to [this tool](https://connect.eng.ansible.com/open_polls/open_polls.html) I created which lists all the currently open polls on the forum.

I’ve added it to the sidebar so you can find it again later, let me know if it needs any updates 😛

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [November 27, 2023, 7:31pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471/26 "2023-11-27T19:31:09Z")

</div>

Since this is the very first vote in the forum, let’s ping [@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee)! Fellow Steering Committee members, please consider the above vote 🙂

---

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [December 3, 2023, 6:02am UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471/27 "2023-12-03T06:02:29Z")

</div>

Hi @gwmngilfen , neat tool, thanks for that!

I just noticed that [Lets try a vote in the SC style - #2 by gotmax23](http://forum.ansible.com/t/150/2) is still showing up, but when we go to that link, the topic itself is closed, so clearly the topic and the poll are not coupled in the sense that the poll should be pointless after the topic is closed. Would that be something easy to achieve? Not demanding, just asking out of curiosity.

---

<div class="post-metadata">

**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\
**Post date:** [December 4, 2023, 11:05am UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471/28 "2023-12-04T11:05:18Z")

</div>

I think that topic closed because I enabled auto-close on the Sandbox while we were playing around, and it hasn’t seen any activity. That isn’t enabled on #Project Discussions so we shouldn’t hit that scenario.

However, to answer your question - no, I don’t think there’s any tooling to link closed polls to closed topics. You could script something using the API of course, but I don’t think there’s anything native.

---

<div class="post-metadata">

**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\
**Post date:** [December 4, 2023, 10:19pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471/29 "2023-12-04T22:19:37Z")

</div>

This vote has been approved! I don’t have permissions to close the voting polls. @mariolenz, can you please take care of that?

**Steering committee** (+7,-0): felixfontein; gotmax23; mariolenz; gundalow; briantist; Andersson007; russoz

**Community** (+5,-0): samccann; gwmngilfen; Leo; cybette; anwesha

 ![Final vote](https://us1.discourse-cdn.com/ansible/original/2X/f/fad73ecc5252b204b18184cf8ada0d9eb91f37a7.png)

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [December 5, 2023, 5:24am UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471/30 "2023-12-05T05:24:42Z")

</div>

I can confirm the vote counts. So this proposal has passed 🎉

---

<div class="post-metadata">

**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\
**Post date:** [December 5, 2023, 9:16am UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471/31 "2023-12-05T09:16:56Z")

</div>

I closed the polls since I was passing. I will look into what permissions are needed to do that, we might be able to do a group thing 🙂

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [December 5, 2023, 3:21pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471/32 "2023-12-05T15:21:01Z")

</div>

Thanks @gotmax23 and @felixfontein for counting! And thanks @gwmngilfen for closing the polls! I wouldn’t have found the time to do it myself up until now.

---

<div class="post-metadata">

**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\
**Post date:** [December 5, 2023, 5:04pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471/33 "2023-12-05T17:04:32Z")

</div>

I’ve merged [Ansible 9: Follow ansible-core more closely by mariolenz · Pull Request #856 · ansible/ansible-documentation · GitHub](https://github.com/ansible/ansible-documentation/pull/856) and will merge the `stable-2.16` backport once CI passes. Thanks everyone!

[Previous page](https://forum.ansible.com/t/vote-ended-on-2023-12-04-release-schedule-for-holiday-releases/2471.md?page=1)
