# Feature freeze for 0.5 / release scheduled for July 4 **URL:** \ **Category:** Ansible Project\ **Created:** [June 29, 2012, 11:05pm UTC](https://forum.ansible.com/t/feature-freeze-for-0-5-release-scheduled-for-july-4/11632 "2012-06-29T23:05:42Z")\ **Posts on this page:** 3\ **Page:** 1
**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 29, 2012, 11:05pm UTC](https://forum.ansible.com/t/feature-freeze-for-0-5-release-scheduled-for-july-4/11632/1 "2012-06-29T23:05:42Z")
Various release-related news and administrative stuff: == Feature Freeze for 0.5 == I'm going to hold any pull requests for features from now until we release 0.5 If anyone has any bug fixes, you have until midnight Tuesday to send me a pull request for those. (If you miss something for 0.5, it's ok, we're still going to try to shoot for one release a month, so you won't have long to wait.) === What's Left for 0.5 and 0.6 Plans == Not much at all is left for 0.5, we have slipped the release a little, so we've had plenty of time, and this is a full release with a lot of good stuff in it, including native SSH support! The bug queue has been \*very\* well cleaned out, thankfully it turned out that many things were already fixed, so the only item I have left to look at for 0.5 in my list is #515, which is about making the path to the setup file more predictable when sudoing to root. This leaves only two open tickets to be punted to 0.6, which I think is wise given they are somewhat non-trivial:    (279) yum installs multiple packages when used with with\_items … I think Seth is looking at the yum side and when that's done I'll take care of the with\_items part    (399) support same hosts on different posts (a forwarding use case) I do not have any hard plans for 0.6, so it will be what folks want it to be, which has worked pretty well for us so far! I may very well peruse some of the pseudo-monitoring/pseudo-big-data ideas I mentioned earlier and see how those turn out. === Testing Welcome == Any testing on 0.5 now in anticipation of the release Wednesday is very very welcome. 0.5 has not evolved super fast lately, so just making sure your existing playbooks are good to go is probably sufficient, and maybe hammer on the --connection=ssh option if you care about the various features the native SSH type will give you (like Kerberos support!) As a reminder the updated change log can be found at: [https://github.com/ansible/ansible/blob/devel/CHANGELOG.md](https://github.com/ansible/ansible/blob/devel/CHANGELOG.md) After the release goes out I'll start updating the documentation to include all of the new 0.5 features. Thanks! --Michael ---
**Author:** ![jpmens1](https://avatars.discourse-cdn.com/v4/letter/j/e9c0ed/32.png) [@jpmens1](https://forum.ansible.com/u/jpmens1)\ **Post date:** [July 3, 2012, 10:11am UTC](https://forum.ansible.com/t/feature-freeze-for-0-5-release-scheduled-for-july-4/11632/2 "2012-07-03T10:11:39Z")
> maybe hammer on the --connection=ssh option if you care about the > various features the native SSH type will give you (like Kerberos > support!) Testing current devel Git branch, I can report that it works for me, (running on Centos 6.2 against OpenSuse 12.1) though I do recommend having ControlMaster connection open to the foreign node(s):         $ kinit f2         Password for f2@EXAMPLE.NET:         $ export ANSIBLE\_SSH\_ARGS=""         $ export ANSIBLE\_REMOTE\_USER=f2         $ time ansible -c ssh su3.example.net -m ping         su3.example.net | success \>\> {             "ping": "pong"         }         real 0m3.312s         user 0m0.394s         sys 0m0.201s         # in another terminal, open and keep open an SSH session         # as user f2 to host su3.example.net, ensuring that         # this connection has controlmaster. (My ~/.ssh/config         # contains         # Host \*         # ControlMaster auto         # ControlPath ~/.ssh/controlmaster/%r@%h:%p         # ).         $ time ansible -c ssh su3.example.net -m ping         su3.example.net | success \>\> {             "ping": "pong"         }         real 0m0.993s         user 0m0.359s         sys 0m0.175s Regards,         -JP ---
**Author:** ![Andreas\_Davour](https://avatars.discourse-cdn.com/v4/letter/a/bcef8e/32.png) [@Andreas\_Davour](https://forum.ansible.com/u/Andreas_Davour)\ **Post date:** [July 3, 2012, 11:02am UTC](https://forum.ansible.com/t/feature-freeze-for-0-5-release-scheduled-for-july-4/11632/3 "2012-07-03T11:02:27Z")
I can also confirm great success with this. Sadly my farm contains a ssh that is too old (from RHEL6.2 to REHL5), so I have to be patient. But, it works! Many thanks for this feature. -andreas