# Ansible release 2.9.0b1, feature freeze, and stable-2.9 branching

**URL:** <https://forum.ansible.com/t/ansible-release-2-9-0b1-feature-freeze-and-stable-2-9-branching/31218>\
**Category:** Ansible Developer\
**Created:** [September 6, 2019, 6:57pm UTC](https://forum.ansible.com/t/ansible-release-2-9-0b1-feature-freeze-and-stable-2-9-branching/31218 "2019-09-06T18:57:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tkuratom](https://avatars.discourse-cdn.com/v4/letter/t/b19c9b/32.png) [@tkuratom](https://forum.ansible.com/u/tkuratom)\
**Post date:** [September 6, 2019, 6:57pm UTC](https://forum.ansible.com/t/ansible-release-2-9-0b1-feature-freeze-and-stable-2-9-branching/31218/1 "2019-09-06T18:57:41Z")

</div>

Hi all- Feature freeze for Ansible-2.9.0 was last week. At that time,  
we also branched stable-2.9 from the devel branch. So features can  
continue to be opened against devel. They just won't be backported to  
stable-2.9.

The creation of the stable branch also means that if you have a bugfix  
that should be applied to the 2.9.0 release, it needs to be backported  
to the stable-2.9 branch after it has been merged into devel.  
Standard rules about backports (no features, higher risk bugfixes will  
be evaluated as to whether the risk outweighs the benefits, and  
backports need to have changelog fragments) apply.

More information on backports can be found here:  
[http://docs.testing.ansible.com/ansible/latest/community/development\_process.html?highlight=backport#backporting-merged-prs](http://docs.testing.ansible.com/ansible/latest/community/development_process.html?highlight=backport#backporting-merged-prs)

Ansible 2.9.0 beta1