On 2014-01-02 10:28:24 -0500 (-0500), Sean Dague wrote: [...] > So lets go after the real problem, selecting subsets of reviews, which > is really a gerrit problem (made worse because we are on an ancient > gerrit. 2.4 is really no longer suitable). [...] So the real > solution is gerrit upgrade, which is currently held up on the WIP > patch. But I think we're getting to the point where we need to > decide if that one feature is worth holding up all the rest of the > features that we are missing that would help with our review > overload problem.
And just to follow up with a pointer to the corresponding Infra ML thread... http://lists.openstack.org/pipermail/openstack-infra/2014-January/000596.html We have a very large code review system with lots of moving parts (many of whom are the hundreds of developers and reviewers interacting with it on a daily basis). There are quite a few of us actively working on the upgrade, and WiP isn't really a blocker at this stage. We're mostly just wanting to make sure we iron out the other hairy bits for upgrading from 2.4.x to 2.8 (or 2.9) and would like to reduce the disruption for our community to an absolute minimum... thus much testing is still outstanding even though we think we've (mostly) ironed out the remaining issues. -- Jeremy Stanley _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
