# Ansible 1.1 release plan -- upcoming feature freeze 3/25, release 4/2 **URL:** \ **Category:** Ansible Project\ **Created:** [March 22, 2013, 1:33am UTC](https://forum.ansible.com/t/ansible-1-1-release-plan-upcoming-feature-freeze-3-25-release-4-2/12555 "2013-03-22T01:33:29Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\ **Post date:** [March 22, 2013, 1:33am UTC](https://forum.ansible.com/t/ansible-1-1-release-plan-upcoming-feature-freeze-3-25-release-4-2/12555/1 "2013-03-22T01:33:29Z")
Hi everyone, It's about time to release Ansible 1.1! I know lots of people run straight from the development branch (no reason to stop!), but a release is still a pretty big milestone, and is consumed by lots of folks running content out of distributions (such as Extras Packages for Enterprise Linux), as well as those downloading with pip from PyPi. For those folks who are new, Ansible runs on a two month release cycle, which was the result of a very scientific survey asking what folks wanted the release cycle to be. In preparation for the release, I am going to not merge any more features submitted after 3/25 to allow all features to be fully tested -- bugfixes can still be taken. Also, since it is going to be Easter weekend (at least for some of us), I'm not going to release on 3/31, but hold things until 4/2, so we have a little more time to test (and also spend time with families and easter bunnies). And I know better than to release on 4/1 🙂 There's a very large crop of pull requests to merge, which I plan to sort through this weekend. Ansible 1.1 brings about 20 more modules, dry run support, interactive playbook step throughs, a new environment keyword for setting environment variables (like proxy support), a chroot connection type for image builds, and conf.d style inventory directories! Everything is remain fully backward compatible with previous releases as always and there is nothing you need to update from a 1.0 playbook. This should be a great release and I hope everyone is excited as I am. Thank you everyone for making this a totally amazing experience and a very fun project to work on!