# Ansible 2.1

**URL:** <https://forum.ansible.com/t/ansible-2-1/20724>\
**Category:** Ansible Developer\
**Created:** [March 1, 2016, 3:25pm UTC](https://forum.ansible.com/t/ansible-2-1/20724 "2016-03-01T15:25:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Franky\_G](https://avatars.discourse-cdn.com/v4/letter/f/bb73d2/32.png) [@Franky\_G](https://forum.ansible.com/u/Franky_G)\
**Post date:** [March 1, 2016, 3:25pm UTC](https://forum.ansible.com/t/ansible-2-1/20724/1 "2016-03-01T15:25:02Z")

</div>

Hello

When will the 2.1 branch be made available?

Regards

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [March 1, 2016, 3:54pm UTC](https://forum.ansible.com/t/ansible-2-1/20724/2 "2016-03-01T15:54:22Z")

</div>

The 2.1 branch is `devel`. The next release is always worked on in `devel`. Once it is released a stable-2.1 branch will be created, and devel will then be for 2.2.

---

<div class="post-metadata">

**Author:** ![Josh\_Smift1](https://avatars.discourse-cdn.com/v4/letter/j/bcef8e/32.png) [@Josh\_Smift1](https://forum.ansible.com/u/Josh_Smift1)\
**Post date:** [March 1, 2016, 4:00pm UTC](https://forum.ansible.com/t/ansible-2-1/20724/3 "2016-03-01T16:00:04Z")

</div>

> The 2.1 branch is `devel`. The next release is always worked on in  
> `devel`. Once it is released a stable-2.1 branch will be created, and  
> devel will then be for 2.2.

Historically, not everything in devel gets into the next stable release,  
right? Is there a way to tell ahead of time what is and isn't going to  
make it? (I don't actually care about any specific thing in this  
particular case, just curious in general.)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-Josh (jbs@care.com)

This email is intended for the person(s) to whom it is addressed and may contain information that is PRIVILEGED or CONFIDENTIAL. Any unauthorized use, distribution, copying, or disclosure by any person other than the addressee(s) is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and delete the message and any attachments from your system.

---

<div class="post-metadata">

**Author:** ![Franky\_G](https://avatars.discourse-cdn.com/v4/letter/f/bb73d2/32.png) [@Franky\_G](https://forum.ansible.com/u/Franky_G)\
**Post date:** [March 1, 2016, 5:19pm UTC](https://forum.ansible.com/t/ansible-2-1/20724/4 "2016-03-01T17:19:19Z")

</div>

Thanks guys for the update

---

<div class="post-metadata">

**Author:** ![Toshio\_Kuratomi](https://avatars.discourse-cdn.com/v4/letter/t/41988e/32.png) [@Toshio\_Kuratomi](https://forum.ansible.com/u/Toshio_Kuratomi)\
**Post date:** [March 1, 2016, 5:58pm UTC](https://forum.ansible.com/t/ansible-2-1/20724/5 "2016-03-01T17:58:53Z")

</div>

Almost everything in devel gets into the next stable release (major  
version... meaning 2.1 next, then 2.2 after that, etc). If we find  
that something is too destabilizing to go into the next release, we  
have to do a revert on devel and then keep it in a holding branch  
until after stable-2.1 branches from devel before putting it back.  
That's a hassle so we almost never do it (nearer to release, we won't  
merge things into devel until after we've forked stable-2.1).

-Toshio