Goose-bot up and running

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I just updated the location of lp:goose to
"lp:~goose-bot/goose/trunk". So the goose trunk is now protected by a
landing bot.


In the immediate term this means that after getting a proposal
reviewed, to land it on trunk you probably want to:
 1) Copy the description into the Commit Message field on the
Launchpad MP. (lbox uses the description as its commit message, while
LP has its own field for it which is used by tarmac)
 2) Set the status of the MP to Approved

Once it is set to Approved, the bot should notice (it wakes up every
minute). And then it will run the goose tests and the juju-core tests
before landing the code.

If we are trying to land a patch that needs concurrent juju-core and
goose updates, you can:

a) land the juju-core patch before submitting for approval, though
this doesn't seem ideal, since it means you explicitly broke juju-core
before goose is updated.

b) do the commits manually (locally, run the test suites, ensure
everything is kosher). Then push to lp:juju-core and
bzr+ssh://goose-bot@bazaar.launchpad.net/~goose-bot/goose/trunk

I added the ssh keys of my team to "goose-bot" so you should have access.


My next step is to look into updating lbox, so that it can do steps
1&2 via a "lbox submit --tarmac" flag.


That, and we can probably set up something like this for juju-core
itself. And once we stabilize, we can look into doing more with
specific versions of goose against juju-core.

Since we are getting close to having openstack officially available in
juju-core, we are probably also getting close to stabilizing.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlEKK2cACgkQJdeBCYSNAAPJ4gCgpQVq68r8tdtMG4A55dL0CeNC
hj0AoJo3rUACMgysnYoS3Ztg4wJHFdLo
=UODj
-----END PGP SIGNATURE-----