<div dir="ltr"><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">+1</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">
I agree that this is a good idea.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Regards,</div><div class="gmail_default" style="font-size:small">Mandeep</div>
<div class="gmail_default" style="font-size:small">----</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Thu, Aug 28, 2014 at 10:13 AM, Jay Pipes <span dir="ltr"><<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">On 08/28/2014 12:50 PM, Michael Still wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Thu, Aug 28, 2014 at 6:53 AM, Daniel P. Berrange <<a href="mailto:berrange@redhat.com" target="_blank">berrange@redhat.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Thu, Aug 28, 2014 at 11:51:32AM +0000, Alan Kavanagh wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
How to do we handle specs that have slipped through the cracks<br>
and did not make it for Juno?<br>
</blockquote>
<br>
Rebase the proposal so it is under the 'kilo' directory path<br>
instead of 'juno' and submit it for review again. Make sure<br>
to keep the ChangeId line intact so people see the history<br>
of any review comments in the earlier Juno proposal.<br>
</blockquote>
<br>
Yes, but...<br>
<br>
I think we should talk about tweaking the structure of the juno<br>
directory. Something like having proposed, approved, and implemented<br>
directories. That would provide better signalling to operators about<br>
what we actually did, what we thought we'd do, and what we didn't do.<br>
</blockquote>
<br></div>
I think this would be really useful.<span class="HOEnZb"><font color="#888888"><br>
<br>
-jay</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</div></div></blockquote></div><br></div>