On 05/03/2012 05:24 AM, Thierry Carrez wrote:
(snip things I pretty much agree with) >> (I'm not sure gerrit is right for this. Why not just do it in >> folk's github forks? I think all people are looking for is for >> people to be more aware of feature branches. How about if you put >> details of your feature branch in the blueprint for the feature?) >> >> (If not using gerrit, can developers configure Jenkins to CI their >> branch? Or is Smokestack the right tool?) > > I think preserving the ability to run your branch through integration > testing is a necessary prerequisite of the new model. Agree, otherwise it gets weird. HOWEVER - I also agree that the current UI as we're presenting it might not be optimal. Let me follow up with some sketched out thoughts on how we can address both concerns. > Thanks again for starting the discussion on this. I'll meet with Jim > Blair (and hopefully Monty) next week to brainstorm solutions, so > discussing the needed properties of the system is a very nice step forward. > > Regards, > _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
