Hi Marcus,
We should fix up the documentation, we renamed 'thirsty' to 'force'
and added thirsty as an alias for backwards compatibility in 1.1.
It seems like your checkout of 1.1 might need a "git pull --rebase" to
bring it up to the latest.
--Michael
Right, changes like these might confuse users (something I didn't think of when switching the alias) but this could be avoided by keeping the documentation after each release in some sort of archive. Or at least separate the development documentation from the stable.
Shouldn't be hard, however we loose a bit of the flexibility we have now. This becomes more important if environments choose to stick to a specific release for a longer period of time. (Ansible is maturing nicely that this may become a necessity)
I bet AnsibleWorks has this already thought through and are in the execution phase ! Right ? 
I bet AnsibleWorks has this already thought through and are in the execution
phase ! Right ?
Execution phase not so much, but overhauling docs is in plan, yes!
So we'll remember to version them too