# (dev) milestone issue list for 0.8, release plan -- need help closing tickets!

**URL:** <https://forum.ansible.com/t/dev-milestone-issue-list-for-0-8-release-plan-need-help-closing-tickets/11945>\
**Category:** Ansible Project\
**Created:** [September 29, 2012, 1:04pm UTC](https://forum.ansible.com/t/dev-milestone-issue-list-for-0-8-release-plan-need-help-closing-tickets/11945 "2012-09-29T13:04:51Z")\
**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:** [September 29, 2012, 1:04pm UTC](https://forum.ansible.com/t/dev-milestone-issue-list-for-0-8-release-plan-need-help-closing-tickets/11945/1 "2012-09-29T13:04:51Z")

</div>

I'm looking to release Ansible 0.8 in mid October, which is pushed  
back only about 2 weeks from our usual schedule.

This will give us time to finish module documentation, fireball mode,  
and squash tickets.

Since we're starting to have a lot of ideas and feature requests open,  
I've organized issues by milestones in github again (think we are  
large enough to want for this)

Here is 0.8

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

For those who can help fix bugs, please take a look at the list and  
help close unassigned tickets.

Items flagged 'blocks next release' are features or bugs that must be  
complete to release 0.8, other issues we can defer until 0.9 if  
needed.

I would definitely like to close any of the bugs that have been open  
for a longer period of time though -- there were some low priority  
items that I'd like to fix so they don't build up.

If everyone here can spend an hour or two knocking out a bug it ends  
up saving me several nights and weekends 🙂

Thanks everyone!

--Michael