# Ansible 1.9.3 rc3 is now available for testing

**URL:** <https://forum.ansible.com/t/ansible-1-9-3-rc3-is-now-available-for-testing/19095>\
**Category:** Ansible Project\
**Created:** [August 24, 2015, 3:01pm UTC](https://forum.ansible.com/t/ansible-1-9-3-rc3-is-now-available-for-testing/19095 "2015-08-24T15:01:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\
**Post date:** [August 24, 2015, 3:01pm UTC](https://forum.ansible.com/t/ansible-1-9-3-rc3-is-now-available-for-testing/19095/1 "2015-08-24T15:01:07Z")

</div>

Hi all, we’ve just tagged the rc3 release for 1.9.3, which includes a fix we neglected to include in rc2 (Eucalyptus support for ec2 modules was broken in a previous release).

To test from source, simply clone the git repository (if you haven’t already) and do the following:

$ git checkout v1.9.3-0.3.rc3  
$ git submodule update  
$ . hacking/env-setup

After which time you can run ansible and ansible-playbook like normal. If you’re not familiar with the hacking/env-setup script, please refer to the documentation here:

[http://docs.ansible.com/intro\_installation.html#running-from-source](http://docs.ansible.com/intro_installation.html#running-from-source)

To make a tar ball, RPM or DEB with which to test, do the following:

$ git checkout v1.9.3-0.3.rc3  
$ git submodule update

# for a .tar.gz (output is dist/ansible-1.9.3.tar.gz)

$ make sdist

# for RPMs

$ OFFICIAL=yes make rpm

# for DEBs

$ OFFICIAL=yes make deb

If you discover any errors related to this release candidate, please open a Github issue and be sure to mention which version you’re testing. We will be looking to evaluate the status of this release candidate on Wednesday, August 26th.

Thanks!