# Stay up to date with what's new in 0.5 so far / release status

**URL:** <https://forum.ansible.com/t/stay-up-to-date-with-whats-new-in-0-5-so-far-release-status/11623>\
**Category:** Ansible Project\
**Created:** [June 20, 2012, 1:43am UTC](https://forum.ansible.com/t/stay-up-to-date-with-whats-new-in-0-5-so-far-release-status/11623 "2012-06-20T01:43:21Z")\
**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:** [June 20, 2012, 1:43am UTC](https://forum.ansible.com/t/stay-up-to-date-with-whats-new-in-0-5-so-far-release-status/11623/1 "2012-06-20T01:43:21Z")

</div>

Since not everything in the development release is available on  
ansible.github.com (the documentation site) yet, so here's (finally) a  
copy of the updated changelog. If you've just recently started  
following things, we aim to release a new version of Ansible every  
month or so, and the version you get by default when you checkout from  
github is the development branch to encourage people to test and  
contribute to the latest.

Here's what is new on the development branch, as of the last month or so:

[https://github.com/ansible/ansible/blob/devel/CHANGELOG.md](https://github.com/ansible/ansible/blob/devel/CHANGELOG.md)

I am happy to say I've done almost NONE of this awesome work. Thank you all.

There are about 12 or so tickets still open in this release, but only  
about 3 or 4 (mostly error handling related) that we actually need to  
close for this release. Many are ideas, which means they can (and  
likely will) get pushed to the next release. As a reminder, if you  
do not see a ticket assigned to someone in github, assume no one is  
going to work on it, and that's an invitation to send in a pull  
request if you'd like to see that issue closed. See here:

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

Going back to the changelog, I especially want to call attention to  
the new "--connection=ssh", which means that we finally have support  
for Kerberos, and various other SSH tricks people like. I view this  
as pretty much the last remaining barrier to adoption for some  
people... I think this more or less makes Ansible appropriate for just  
about everyone. It's a really big deal for gathering new users and  
contributors. A huge thanks to dhozac for writing this and many  
others for helping test.

Paramiko will remain the default for various reasons -- namely I am  
not sure EVERYONE is running ansible on an SSH that supports  
ControlMaster, which is essentially required for using  
'--connection-ssh', and it's new. Also right now the paramiko  
connection is the only one that can support --ask-pass, (not true for  
--ask-sudo-pass, which it does support), though this might change in  
the future. There many be other reasons later, most likely we'd  
consider changing the default several releases before paramiko would  
be dropped.

I am still looking to release 0.5 sometime in early July.