What can I do to help you guys out?
> The main problem with TravisCI is that it doesn't actually test what you > woukd finally land if trunk gets ahead of your branch. (When you propose a > branch it merges trunk at that time and then tells you the test results. > But if you get more trunk revs, it doesn't re test.) We're used to a bot > that controls trunk, so we know the test suite passed when a given > revision > lands on trunk. > We could live with and make it work if it was the only option, but > Juju-GUI > has a different lander that works more how we would expect. (It requires > more set up and hosting the stuff ourselves, but it works closer to how > we > would expect.) > Gerrit might also be an option, but I'm hoping we can do pieces at a > time. > > John > =:-> > On Mar 14, 2014 10:33 PM, "Jonathan Aquilina" <jaquil...@eagleeyet.net> > wrote: > >> 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 >> > <jaquil...@eagleeyet.net>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 >> >> > Juju-dev@lists.ubuntu.com >> >> > Modify settings or unsubscribe at: >> >> > https://lists.ubuntu.com/mailman/listinfo/juju-dev >> >> > >> >> >> >> >> >> >> >> -- >> >> Juju-dev mailing list >> >> Juju-dev@lists.ubuntu.com >> >> Modify settings or unsubscribe at: >> >> https://lists.ubuntu.com/mailman/listinfo/juju-dev >> >> >> > >> >> >> >> -- >> Juju-dev mailing list >> Juju-dev@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev >> > -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
