I am happy to hear this. We are discussing using github internally as well.
Jan On Jul 28, 2011, at 1:28 PM, Trey Morris <[email protected]> wrote: > well I'm excited about it! > > On Mon, Jul 18, 2011 at 4:20 PM, Monty Taylor <[email protected]> wrote: > On 07/18/2011 02:59 PM, Andy Smith wrote: > Jay and Monty, could you give the list an update on the status and > timeline of the GitHub migration? > > Things are going quite swimingly. Proof of concept went well and we've been > working on starting to roll some things out. > > We've moved the CI repos (github.com/openstack/openstack-ci and > github.com/openstack/openstack-ci-puppet) to be managed via Jenkins/Gerrit > (so that we're eating our own dogfood) as we're currently working with the > Keystone team to move their stuff in (since they're already on github, and > since they are not already using tooling, they're an easier subset of the > migration) We're going to let those bake for a few days so that we can make > sure there aren't major trainwrecks either in the system itself or in the > documentation before starting to move the larger projects. > > Next we'll move a project that is currently on launchpad using tarmac - I'm > voting for either Glance or Burrow. Specifically the need here is sorting out > tarballs/packaging on a lower-traffic project. > > Once THAT is done, we should be in good enough shape to move the larger > projects like Nova. > > > The last informal estimate I had heard was that July 15th was the > planned date. What are the current issues? > > That's not too far off, actually. We sent out the intro instructions to the > keystone team on the 15th - so you can consider things in motion. > > We've got blueprints up on our current items in work at: > > https://blueprints.launchpad.net/openstack-ci > > The blueprint's in question here are: > > https://blueprints.launchpad.net/openstack-ci/+spec/ci-git-support > > and > > https://blueprints.launchpad.net/openstack-ci/+spec/ci-git-transition > > There are several things we will continue to hack on in terms of > enhancements, but there is no need for those to block the continued rollout > of things. On the other hand, we know of a couple that will involve small > workflow changes, and we're trying to get _those_ done before we migrate > everybody. > > I'd say the largest issue I want to see done before we get to Nova is > listening for +2 events in the event stream from Jenkins. (which should not > be hard to do) I'd love to get a few things sorted around auth/users and > groups - but I'm gonna guess that we won't see that before the final > transition. > > SO - all of that to say - things have begun migrating, and it will be a > little while longer before we get to nova. > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
