# Feature freeze for 0.4 in effect **URL:** \ **Category:** Ansible Project\ **Created:** [May 11, 2012, 10:25pm UTC](https://forum.ansible.com/t/feature-freeze-for-0-4-in-effect/11536 "2012-05-11T22:25:45Z")\ **Posts on this page:** 4\ **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:** [May 11, 2012, 10:25pm UTC](https://forum.ansible.com/t/feature-freeze-for-0-4-in-effect/11536/1 "2012-05-11T22:25:45Z")
Any pull requests not already received will be merged into the 0.5 devel branch once we release 0.4, along with possibly a few already recieved. Bugfixes of reasonable size are still fair game. –Michael ---
**Author:** ![Jim\_Richardson](https://avatars.discourse-cdn.com/v4/letter/j/d07c76/32.png) [@Jim\_Richardson](https://forum.ansible.com/u/Jim_Richardson)\ **Post date:** [May 12, 2012, 12:16am UTC](https://forum.ansible.com/t/feature-freeze-for-0-4-in-effect/11536/2 "2012-05-12T00:16:05Z")
No ANSIBLE\_REMOTE\_TMPDIR in 0.4? ---
**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 12, 2012, 12:18am UTC](https://forum.ansible.com/t/feature-freeze-for-0-4-in-effect/11536/3 "2012-05-12T00:18:28Z")
That’s a very small change, so I’m willing to treat it as a bug fix. See if you can get [https://github.com/ansible/ansible/pull/347](https://github.com/ansible/ansible/pull/347) resolved by the middle of next week. I’d like to release sometime next week after giving people some time to pound on the current code. ---
**Author:** ![Jim\_Richardson](https://avatars.discourse-cdn.com/v4/letter/j/d07c76/32.png) [@Jim\_Richardson](https://forum.ansible.com/u/Jim_Richardson)\ **Post date:** [May 12, 2012, 12:57am UTC](https://forum.ansible.com/t/feature-freeze-for-0-4-in-effect/11536/4 "2012-05-12T00:57:45Z")
Done, PR generated.