If you guys need help I have some experience with github and would love to help you guys out with setting up gerrit for code review as well as continuous integration as well provided by travis CI.
> My current understanding is that we are pushing hard towards a new stable > release, and then towards a 2.0 release candidate in the next few weeks. > We > are likely to do the github switch right after that, so my estimation > would > be that the switch will be done mid-april. > > --Mark Ramm > > > On Fri, Mar 14, 2014 at 1:19 PM, Jonathan Aquilina > <[email protected]>wrote: > >> For code review there is gerrit >> >> https://code.google.com/p/gerrit/ >> >> I have seen this used by the libreoffice project, and its very >> successful >> as there can be multiple people reviewing patches which get submitted. >> it >> integrates with any git version control and already github has a hook >> available to integrate it easily with ones github repo >> >> > It seems there has been some interest in moving juju-core from bazaar >> on >> > launchpad to git on github? >> > >> > Also, it seems like the main sticking point is the need for a >> generally >> > accepted code review tool/process. >> > >> > I'd like to see the code over on github; what can I do to help make it >> > happen? >> > >> > Sounds like a good code review tool is a starting point? >> > >> > Cheers, >> > >> > -- >> > John Weldon >> > -- >> > Juju-dev mailing list >> > [email protected] >> > Modify settings or unsubscribe at: >> > https://lists.ubuntu.com/mailman/listinfo/juju-dev >> > >> >> >> >> -- >> Juju-dev mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev >> > -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
