As we're starting to see more active development of clusto by more participants, I wanted to get everybody on the same page. To that effect, I merged all of the reasonable looking things I could find on github. The following branches were integrated into clusto/master:
rongoro/feature/ec2support was merged into synack/master and simplegeo/pending before any of this, so those changes were picked up as well (and account for a large chunk of this merge).
The new version is tagged as release-0.5.33-1 and should be considered the most up-to-date release of clusto available. Any new patches to be applied to clusto/master should be rebased on this tag before submitting a pull request.
I'll be spending some time this week cleaning up our debian and python dependencies lists to make it a bit easier to get clusto running. We've let a lot of one-off things creep in that should really be soft dependencies.
Let me know if this has seriously disrupted or hindered anybody's progress on clusto.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
-----END PGP SIGNATURE-----
So wait, what exactly is the release procedure/policy for clusto? I
think what you're saying is that if I pull from github.com/clusto/clusto
branch master, I'll get your argparse stuff, but it's still
development/beta code. If I want the latest stable, I need to pull from
release-0.5.33-1, if I understand right. Is that correct?
In the future, should I expect to see announcements on this list when a
new stable version is tagged?