On Tue, Aug 12, 2014 at 9:56 AM, Mark McLoughlin <markmc at redhat.com> wrote: > Hey > > (Terrible name for a policy, I know) > > From the version_cap saga here: > > https://review.openstack.org/110754 > > I think we need a better understanding of how to approach situations > like this. > > Here's my attempt at documenting what I think we're expecting the > procedure to be: > > https://etherpad.openstack.org/p/nova-retrospective-veto-revert-policy > > If it sounds reasonably sane, I can propose its addition to the > "Development policies" doc. > Thanks for the write up, Mark. When I first read the thread I thought it'd be about the case where a core takes a vacation or is unreachable _after_ marking a review -2. Can this case be considered in this policy as well (or is it already and I don't know it?) Thanks, Anne > > Mark. > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140812/4af2882c/attachment.html>