Whoops, forgot to include the submodule update step again. Here is the updated checkout steps:
$ git checkout v1.9.0-0.2.rc2 $ git submodule update Be sure to do that whether sourcing the hacking script, or if building a tar/RPM/DEB. James Cammarata Director, Ansible Core Engineering github: jimi-c On Fri, Mar 20, 2015 at 3:05 PM, James Cammarata <[email protected]> wrote: > Hi all, we've just tagged the rc2 release for 1.9 > To test from source, simply clone the git repository (if you haven't > already) and do the following: > > $ git checkout v1.9.0-0.2.rc2 > $ . 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 > > To make a tar ball, RPM or DEB with which to test, do the following: > > $ git checkout v1.9.0-0.2.rc2 > > # for a .tar.gz (output is dist/ansible-1.9.0.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 next Tuesday, > March 24th, at which time we will decide if we will cut the final release > or if we need to do an rc3 release. > > Thanks! > > James Cammarata > Director, Ansible Core Engineering > github: jimi-c > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAMFyvFiRxUp48FE4Trb%3Dipkqoq-GnVe1WOW9DPwU_dPA%3DAOD2A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
