# Feature freeze merging complete -- changelog updated, docs in progress **URL:** \ **Category:** Ansible Project\ **Tags:** ubuntu\ **Created:** [January 26, 2013, 6:38pm UTC](https://forum.ansible.com/t/feature-freeze-merging-complete-changelog-updated-docs-in-progress/12252 "2013-01-26T18:38:19Z")\ **Posts on this page:** 6\ **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:** [January 26, 2013, 6:38pm UTC](https://forum.ansible.com/t/feature-freeze-merging-complete-changelog-updated-docs-in-progress/12252/1 "2013-01-26T18:38:19Z")
I've merged in a ton of new things this morning and have also rebuilt the docsite to account for the new modules. Seeing the 0 pull request counter in github feels good! The mostly-organized changelog details what is coming, though work on updating docs for 1.0 still remains. Those who would like to help test for the final release can see a list of all that is new here -- [https://github.com/ansible/ansible/blob/devel/CHANGELOG.md](https://github.com/ansible/ansible/blob/devel/CHANGELOG.md) We have a large amount of users so I'd say just test what content you normally use, and anything new that happens to look interesting! Lots of changes related to EC2 integration lately, which is good stuff. Thanks to the folks from Eucalyptus Systems for that, among others. Note new modules for pkgin (Joyent SmartOS), pacman (Arch Linux), sysctl, mercurial ("hg"), and apt\_key (Debian/Ubuntu) also! --Michael ---
**Author:** ![Dag\_Wieers](https://avatars.discourse-cdn.com/v4/letter/d/45deac/32.png) [@Dag\_Wieers](https://forum.ansible.com/u/Dag_Wieers)\ **Post date:** [February 18, 2013, 4:11pm UTC](https://forum.ansible.com/t/feature-freeze-merging-complete-changelog-updated-docs-in-progress/12252/2 "2013-02-18T16:11:09Z")
It feels less if your pull request didn't make it though 😉 ---
**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:** [February 18, 2013, 4:16pm UTC](https://forum.ansible.com/t/feature-freeze-merging-complete-changelog-updated-docs-in-progress/12252/3 "2013-02-18T16:16:53Z")
which one was that? ---
**Author:** ![Dag\_Wieers](https://avatars.discourse-cdn.com/v4/letter/d/45deac/32.png) [@Dag\_Wieers](https://forum.ansible.com/u/Dag_Wieers)\ **Post date:** [February 18, 2013, 4:25pm UTC](https://forum.ansible.com/t/feature-freeze-merging-complete-changelog-updated-docs-in-progress/12252/4 "2013-02-18T16:25:21Z")
I was mostly joking. One of them was #1801, the discussion died down (new contract, paternity leave ;-)). The discussed solution is not something that would have worked for me. I still believe we ought to have a way to control whether we want a pty or not for shell/command as the original patch did. But if I come across the need again, I am going to propose it once more:      [https://github.com/ansible/ansible/pull/1801#issuecomment-11667792](https://github.com/ansible/ansible/pull/1801#issuecomment-11667792) 😉 ---
**Author:** ![Dag\_Wieers](https://avatars.discourse-cdn.com/v4/letter/d/45deac/32.png) [@Dag\_Wieers](https://forum.ansible.com/u/Dag_Wieers)\ **Post date:** [February 18, 2013, 4:27pm UTC](https://forum.ansible.com/t/feature-freeze-merging-complete-changelog-updated-docs-in-progress/12252/5 "2013-02-18T16:27:00Z")
I should have said:    Now that dry-run has been accepted, anything is open for debat again ? 😉 ---
**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:** [February 18, 2013, 6:22pm UTC](https://forum.ansible.com/t/feature-freeze-merging-complete-changelog-updated-docs-in-progress/12252/6 "2013-02-18T18:22:34Z")
> I should have said: > >         Now that dry-run has been accepted, anything is open for debat again > ? Yes, it finally became easy enough to do, I think, that we could manage the distraction, and I found a way to do it that would not require it of all modules. Ponies are fair game to discuss, but perhaps no Clydesdales, as I am told they get too big. Thanks for prodding me. Again, there are lots of limitations that mean this won't work for everyone, and the caveats apply, but I got tired of hearing "Ansible can't do X", so we made it do X 🙂