# Expected time for bug fixes to be released? **URL:** \ **Category:** Ansible Developer\ **Created:** [August 28, 2015, 7:16pm UTC](https://forum.ansible.com/t/expected-time-for-bug-fixes-to-be-released/19138 "2015-08-28T19:16:33Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![joel](https://avatars.discourse-cdn.com/v4/letter/j/b9bd4f/32.png) [@joel](https://forum.ansible.com/u/joel)\ **Post date:** [August 28, 2015, 7:16pm UTC](https://forum.ansible.com/t/expected-time-for-bug-fixes-to-be-released/19138/1 "2015-08-28T19:16:33Z")
I encountered a bug in 1.9.2, did some digging, and found that a fix had been merged into ‘devel’ more than 16 months ago. However, it has still not made it into a released version of ansible. More details in the issue I entered: [https://github.com/ansible/ansible/issues/12068](https://github.com/ansible/ansible/issues/12068) What is the expected time for this sort of bug fix to be released? Thanks! Joel ---
**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\ **Post date:** [September 3, 2015, 12:16pm UTC](https://forum.ansible.com/t/expected-time-for-bug-fixes-to-be-released/19138/2 "2015-09-03T12:16:21Z")
Hi Joel, 2.0 is currently in alpha, and we’re aiming for a release this fall. ---
**Author:** ![joel](https://avatars.discourse-cdn.com/v4/letter/j/b9bd4f/32.png) [@joel](https://forum.ansible.com/u/joel)\ **Post date:** [September 3, 2015, 2:04pm UTC](https://forum.ansible.com/t/expected-time-for-bug-fixes-to-be-released/19138/3 "2015-09-03T14:04:12Z")
OK, so 1.5 years between a bug with patch submitted and actual release containing it. I’ll plan accordingly. Thanks! ---
**Author:** ![Jesse\_Keating](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@Jesse\_Keating](https://forum.ansible.com/u/Jesse_Keating)\ **Post date:** [September 3, 2015, 3:08pm UTC](https://forum.ansible.com/t/expected-time-for-bug-fixes-to-be-released/19138/4 "2015-09-03T15:08:33Z")
Snarkiness aside, the 2.0 release cycle is a bit of an anomaly. 2.0 changes quite a bit, so the time to release is pretty conservative. That your change got wrapped up into the 2.0 release is unfortunate, but not indicative of future release cycles. Prior to 2.0 the releases were more frequent, and critical bugs were pushed out in even more frequent minor releases. That said, much of Ansible is designed so that bug fixes or enhancements can be made use of easily without waiting for an official release from Ansible. ---
**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\ **Post date:** [September 3, 2015, 4:26pm UTC](https://forum.ansible.com/t/expected-time-for-bug-fixes-to-be-released/19138/5 "2015-09-03T16:26:35Z")
Hey Joel, we went back to try and figure out what happened, and figured it out. This was actually only merged in on April 1st of this year, but was done on devel, so this went into what became the v1 directory of dead code - it was not cherry-picked to stable-1.9. We’re going ahead and correcting that now, so this patch will be included in 1.9.3-1, which we’re going to release today. Sorry for the mix-up! ---
**Author:** ![joel](https://avatars.discourse-cdn.com/v4/letter/j/b9bd4f/32.png) [@joel](https://forum.ansible.com/u/joel)\ **Post date:** [September 3, 2015, 4:28pm UTC](https://forum.ansible.com/t/expected-time-for-bug-fixes-to-be-released/19138/6 "2015-09-03T16:28:56Z")
Hot dog! I \_thought\_ something seemed odd about this particular case. Thanks so much! Joel