<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">25.06.2015 14:58, Sergey Nikitin пишет:<br>
</div>
<blockquote
cite="mid:CAM25k1Rw00JMyqTuSMVt=crEM=mSGFjZ3SGg+Q9kPKry03Nqmg@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span
class="">
<blockquote class="gmail_quote" style="margin:0px 0px
0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0px 0px
0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
I've repeatedly stated that the fact that we created
an even smaller<br>
clique of people to approve specs (nova-drivers
which is a tiny subset<br>
of the already faaaar too small nova-core) is
madness, as it creates<br>
an even worse review burden on them, and thus
worsens the bottleneck<br>
than we already have.<br>
</blockquote>
</blockquote>
<br>
</span>
I agree that the number of people who can approve specs is
too small at the moment. <span
style="font-size:12.8000001907349px">But relatively few
people are actually reviewing </span><span class=""
style="font-size:12.8000001907349px;background-color:rgb(255,255,255)">specs</span><span
style="font-size:12.8000001907349px"> so building trust
here is difficult. </span></blockquote>
<div><br>
</div>
<div><span style="color:rgb(0,0,0);white-space:pre-wrap">I
agree that the number of people who can approve specs is
too small at the moment too. But I disagree that we have
few people who actually reviews specs. </span></div>
<div><span style="white-space:pre-wrap;color:rgb(0,0,0)"><br>
</span></div>
<div><span style="white-space:pre-wrap;color:rgb(0,0,0)">For
example I had a spec (approved for Juno and Kilo, but
not approved for Liberty) <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/177112/">https://review.openstack.org/#/c/177112/</a>
which has nine +1 and zero +2. I implemented this spec a
long time ago but I spent about 2 months to reaprove
spec in Liberty. And it's not reapproved yet.</span></div>
<div><span style="white-space:pre-wrap;color:rgb(0,0,0)"><br>
</span></div>
</div>
</div>
</div>
</blockquote>
<br>
I think it is a good example of improper approach to specs
repository structure. Since specs are tied to release cycle, one
should create specs for a new release cycle from scratch loosing all
the history of considerations and discussion that happened in the
past. It would be much better if corresponding to specs blueprints
were responsible for tagging specs to particular release cycle,
while unimplemented specs remained unmerged until their blueprints
get status implemented. This would make it possible to reflect any
differences that appear during code review in comparison with
original spec.<br>
<br>
<blockquote
cite="mid:CAM25k1Rw00JMyqTuSMVt=crEM=mSGFjZ3SGg+Q9kPKry03Nqmg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><span style="white-space:pre-wrap;color:rgb(0,0,0)">Especially
strange for me is that not all nova cores have core
status in nova-specs repository. Now we have 14 nova
cores and only 7 nova-spec cores. I think if a
contributor worked hard to become a nova core, he or she
is competent to get a nova-spec core status.</span></div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>