Greetings all, we’re working hard to get Ansible-2.1 feature frozen on April 18th. We will do an rc1 on the 18th or 19th. So, committers if there are new modules and new features that you want to get merged in, this is the week to do it.
Non-committers, if there’s feature PRs that you want to get merged, now is the time to get the attention of committers to get those merged. The most reliable way to do that is probably via ansible-devel in IRC but if you can’t get there then pinging here or on the bugs is better than just relying on us to remember all of those ourselves.
As with past Ansible releases we always preten^W hope that the first tarball build for the release could be perfect and therefore we name it rc1. However, in practice, there’s always bugs to fix that we either don’t get to in time for rc1 or that don’t get reported until afterwards. So if you have an open bugfix PR or bug report that affects a large portion of the userbase don’t start panicing yet. We will create future rc’s to address more bugs. Do start to make up lists of those and start prioritising so that you can help us integrate them once we’ve all finished the mad rush towards feature freeze. (Committers, of course, can merge bugfixes at any time).
And yes, sending out this reminder/announcement a week before freeze is a little tight. I think we’d talked about it so much in the past few weeks of video team meetings that we didn’t realize that no one had sent out an official notice before this. yet another reason we’re going to be getting back to public IRC team/contributor meetings starting this week.
-Toshio