# only 4 bugs left in the 0.4 open issues queue!

**URL:** <https://forum.ansible.com/t/only-4-bugs-left-in-the-0-4-open-issues-queue/11527>\
**Category:** Ansible Project\
**Created:** [May 10, 2012, 2:06am UTC](https://forum.ansible.com/t/only-4-bugs-left-in-the-0-4-open-issues-queue/11527 "2012-05-10T02:06:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [May 10, 2012, 2:06am UTC](https://forum.ansible.com/t/only-4-bugs-left-in-the-0-4-open-issues-queue/11527/1 "2012-05-10T02:06:20Z")

</div>

[https://github.com/ansible/ansible/issues?milestone=2&state=open](https://github.com/ansible/ansible/issues?milestone=2&state=open)

I'll be fixing #288 along with lots of docs this weekend.

I see no reason we can't tag the release two or three days after this drops to zero, which may be a week or more early depending on what people want to take on.

Thanks all for help squashing bugs.

Again (beating a dead horse), be sure to help test things posted in my previous email.

Features that drop in at the end of the release need the most testing, because they are the less apt to be used for a long period of time.

You can also look at the CHANGELOG.md file in the checkout and things towards the bottom are newer.

--Michael