<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">Hello Devananda</span><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Design spec for the remote firmware setting feature is under review ( <a href="https://review.openstack.org/#/c/101122" target="_blank">https://review.openstack.org/#/c/101122</a> ). Have received comments on the APIs and we are converging on the set of required APIs.</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Have posted the new patch addressing the comments on the same. </div><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">Please check, if we can re-prioritize this for Juno release.</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">
Thanks and Regards</div><div style="font-family:arial,sans-serif;font-size:13px">Shiv</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 1, 2014 at 4:15 PM, Shivanand Tendulker <span dir="ltr"><<a href="mailto:stendulker@gmail.com" target="_blank">stendulker@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 dir="ltr">Hello Devananda<div><br></div><div>Design spec for the remote firmware setting feature is under review ( <a href="https://review.openstack.org/#/c/101122" target="_blank">https://review.openstack.org/#/c/101122</a> ). Have received comments on the APIs and we are converging on the set of required APIs.</div>
<div><br></div><div>Have posted the new patch addressing the comments on the same. </div><div><br></div><div>Please check, if we can re-prioritize this for Juno release.</div><div><br></div><div>Thanks and Regards</div><div>
Shiv<div><div class="h5"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 1, 2014 at 4:05 PM, Ramakrishnan G <span dir="ltr"><<a href="mailto:rameshg87.openstack@gmail.com" target="_blank">rameshg87.openstack@gmail.com</a>></span> wrote:<br>
<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"><div dir="ltr"><br><br><div class="gmail_quote">---------- Forwarded message ----------<br>
From: <b class="gmail_sendername">Devananda van der Veen</b> <span dir="ltr"><<a href="mailto:devananda.vdv@gmail.com" target="_blank">devananda.vdv@gmail.com</a>></span><br>
Date: Tue, Jul 1, 2014 at 3:42 AM<br>Subject: [openstack-dev] [Ironic] Juno priorities and spec review timeline<br>To: OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<br><br>Hi all!<br>
<br>
We're roughly at the midway point between summit and release, and I<br>
feel that's a good time to take a look at our progress compared to the<br>
goals we set out at the design summit. To that end, I re-opened my<br>
summit notes about what features we had prioritized in Atlanta, and<br>
engaged many the core reviewers in a discussion last friday to<br>
estimate what we'll have time to review and land in the remainder of<br>
this cycle. Based on that, I've created this spreadsheet to represent<br>
those expectations and our current progress towards what we think we<br>
can achieve this cycle:<br>
<br>
<a href="https://docs.google.com/spreadsheets/d/1Hxyfy60hN_Fit0b-plsPzK6yW3ePQC5IfwuzJwltlbo" target="_blank">https://docs.google.com/spreadsheets/d/1Hxyfy60hN_Fit0b-plsPzK6yW3ePQC5IfwuzJwltlbo</a><br>
<br>
Aside from several cleanup- and test-related tasks, these goals<br>
correlate to spec reviews that have already been proposed. I've<br>
crossed off ones which we discussed at the summit, but for which no<br>
proposal has yet been submitted. The spec-review team and I will be<br>
referring to this to help us prioritize specs reviews. While I am not<br>
yet formally blocking proposals which do not fit within this list of<br>
priorities, the review team is working with a large back-log and<br>
probably won't have time to review anything else this cycle. If you're<br>
concerned that you won't be able to land your favorite feature in<br>
Juno, the best thing you can do is to participate in reviewing other<br>
people's code, join the core team, and help us accelerate the<br>
development process of "K".<br>
<br>
Borrowing a little from Nova's timeline, I have proposed the following<br>
timeline for Ironic. Note that dates listed are Thursdays, and numbers<br>
in parentheses are weeks until feature freeze.<br>
<br>
You may also note that I'll be offline for two weeks immediately prior<br>
to the Juno-3 milestone, which is another reason why I'd like the core<br>
review team to have a solid plan (read: approved specs) in place by<br>
Aug 14.<br>
<br>
<br>
<br>
July 3 (-9): spec review day on Wednesday (July 2)<br>
focus on landing specs for our priorities:<br>
<a href="https://docs.google.com/spreadsheets/d/1Hxyfy60hN_Fit0b-plsPzK6yW3ePQC5IfwuzJwltlbo" target="_blank">https://docs.google.com/spreadsheets/d/1Hxyfy60hN_Fit0b-plsPzK6yW3ePQC5IfwuzJwltlbo</a><br>
<br>
Jul 24 (-6): Juno-2 milestone tagged<br>
new spec proposal freeze<br>
<br>
Jul 31 (-5): midcycle meetup (July 27-30)<br>
<a href="https://wiki.openstack.org/wiki/Sprints/BeavertonJunoSprint" target="_blank">https://wiki.openstack.org/wiki/Sprints/BeavertonJunoSprint</a><br>
<br>
Aug 14 (-3): last spec review day on Wednesday (Aug 13)<br>
<br>
Aug 21 (-2): PTL offline all week<br>
<br>
Aug 28 (-1): PTL offline all week<br>
<br>
Sep 4 ( 0): Juno-3 milestone tagged<br>
Feature freeze<br>
K opens for spec proposals<br>
Unmerged J spec proposals must rebase on K<br>
Merged J specs with no code proposed are deleted and may<br>
be re-proposed for K<br>
Merged J specs with code proposed need to be reviewed for<br>
feature-freeze-exception<br>
<br>
Sep 25 (+3): RC 1 build expected<br>
K spec reviews start<br>
<br>
Oct 16 (+6): Release!<br>
<br>
Oct 30 (+8): K summit spec proposal freeze<br>
K summit sessions should have corresponding spec proposal<br>
<br>
Nov 6 (+9): K design summit<br>
<br>
<br>
Thanks!<br>
Devananda<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div><br></div>
</blockquote></div><br></div></div></div></div></div>
</blockquote></div><br></div>