# Need fix in core modules not included with latest release

**URL:** <https://forum.ansible.com/t/need-fix-in-core-modules-not-included-with-latest-release/19107>\
**Category:** Ansible Project\
**Created:** [August 25, 2015, 9:32am UTC](https://forum.ansible.com/t/need-fix-in-core-modules-not-included-with-latest-release/19107 "2015-08-25T09:32:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tore\_Olsen](https://avatars.discourse-cdn.com/v4/letter/t/b5e925/32.png) [@Tore\_Olsen](https://forum.ansible.com/u/Tore_Olsen)\
**Post date:** [August 25, 2015, 9:32am UTC](https://forum.ansible.com/t/need-fix-in-core-modules-not-included-with-latest-release/19107/1 "2015-08-25T09:32:55Z")

</div>

Hi all,

I guess I’m just confused about how the core modules are coordinated with ansible releases.

On April 26, Martin Froelich committed 4bcbcc886936ac7c672a230dec80ac14b6e12211 which fixed a

problem that I’m also experiencing with EC2 profiles. This commit only exists on the devel branch

of ansible-modules-core. I just checked out v1.9.3-0.3.rc3, cherry-picked 4bcbcc8 and did make install

with success and happiness as a result.

I guess someone at ansible decides what to merge into e.g stable-1.9 which seems to be what

eventually is included with the latest ansible release. What’s the reason the above commit hasn’t

made it into release, and may I ask the maintainers to please consider doing this?

Regards,

Tore Olsen