Time for another release!

[Clint Byrum]

So, we released "galapagos", a.k.a. 0.5.1, and that went relatively smoothly.

It has been quite a long time though, nearly 2 months now, since that
release. Since then we've seen some exciting stuff land in juju including
the native OpenStack provider and an initial implementation of "format 2".

I'd like to suggest that we cut *two* releases shortly:

1) 0.5.2 - We missed a couple of fixes in 0.5.1 because of the desire to get it out the
   door. We also forgot to bump the version in setup.py, making life difficult for those
   who are using setup.py to distribute juju. So I think we should create a new series
   in launchpad called '0.5' and cut 0.5.2 from that. We should merge in anything that
   we intend to push into precise as an SRU. This includes:

   * Fix setup.py to say 0.5.2
   * Stop deleting security groups on destroy-env
   * OpenStack provider (We're pushing this as a "hardware enablement" SRU
   * Local provider stop creating a run-away juju machine agent

2) "honolulu", or, 0.6 - With format: 2 for charms, we have a new
   backward-incompatible feature that users can make use of. I know that
   there has been some talk of changing what format: 2 is. If thats the
   case, then this release should be delayed until that is resolved. There
   are a number of other fixes and changes that don't really make up
   enough for a feature-bump release, but aren't important enough for
   a patch release.

Thoughts? If this sounds like a good plan I am thinking we will target 2
weeks from today as the 'freeze' day for both, with a release happening
a week after that.