# Understanding ansible branching model

**URL:** <https://forum.ansible.com/t/understanding-ansible-branching-model/20594>\
**Category:** Ansible Project\
**Created:** [February 16, 2016, 8:50pm UTC](https://forum.ansible.com/t/understanding-ansible-branching-model/20594 "2016-02-16T20:50:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Baydoun](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@Michael\_Baydoun](https://forum.ansible.com/u/Michael_Baydoun)\
**Post date:** [February 16, 2016, 8:50pm UTC](https://forum.ansible.com/t/understanding-ansible-branching-model/20594/1 "2016-02-16T20:50:43Z")

</div>

Can anyone point me to a doc or site that details what branching model the ansible project is following?  
I’d like to better understand what I’m seeing in the github repository, and apply some of that to our internal workflow if appropriate and useful.

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [February 22, 2016, 9:17pm UTC](https://forum.ansible.com/t/understanding-ansible-branching-model/20594/2 "2016-02-22T21:17:23Z")

</div>

No doc or site, the model also has changed as of 1.9., so this is what we currently do:

Mainly we develop against the /devel branch, once we are ready to release we create the stable-x.x branch and release from there (release candidates and finals get tagged here), also subsequent bug fixes will be cherry-picked into it for x.x.x releases.

---

<div class="post-metadata">

**Author:** ![Michael\_Baydoun](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@Michael\_Baydoun](https://forum.ansible.com/u/Michael_Baydoun)\
**Post date:** [February 23, 2016, 1:11am UTC](https://forum.ansible.com/t/understanding-ansible-branching-model/20594/3 "2016-02-23T01:11:34Z")

</div>

Thanks Brian
