<div dir="ltr">Hi, Dmitry,<div><br></div><div><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">I guess the whole idea of new release models is NOT to tie projects to each other any more except for The Big Release twice a year :) So I think no, we don't need to. We still can do it, if we have something to release by the time Ironic releases, but I suggest deciding it on case-by-case basis.</blockquote><div>OK, I see.</div><div><br></div><div>One more concern, about Tempest integration test which I will implement in V2.1.0,</div></div><div>it seems like that we cannot add Ironic-inspector's tests into Tempest even if integration tests.</div><div>Please see:</div><div><a href="https://etherpad.openstack.org/p/YVR-QA-in-the-big-tent">https://etherpad.openstack.org/p/YVR-QA-in-the-big-tent</a><br></div><div><br></div><div>But I heard from you that Devananda thinks we need this in tempest itself. [3]</div><div>Do you know something like current situation?</div><div><br></div><div><br></div><div>Best Regards,</div><div>Yuiko Takada</div><div class="gmail_extra"><br><div class="gmail_quote">2015-06-09 15:59 GMT+09:00 Dmitry Tantsur <span dir="ltr"><<a href="mailto:dtantsur@redhat.com" target="_blank">dtantsur@redhat.com</a>></span>:<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"><span class="">On 06/09/2015 03:49 AM, Yuiko Takada 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">
Hi, Dmitry,<br>
<br>
Thank you for notifying.<br>
<br>
I've updated our summit etherpad [3] with whatever priorities I<br>
remembered, please have a look. I've also untargeted a few things in<br>
launchpad [4] (and will probably untarget more later on). Please<br>
assign yourself, if you want something done in this release time frame.<br>
<br>
I've assigned one item to myself in [3], and also I added one BP to [4],<br>
so please take a look.<br>
<a href="https://blueprints.launchpad.net/ironic-inspector/+spec/delete-db-api" target="_blank">https://blueprints.launchpad.net/ironic-inspector/+spec/delete-db-api</a><br>
</blockquote>
<br></span>
Looks good, though I don't think it's a big priority for 2.0.0. Definitely worth doing for 2.1.0.<br>
<br>
Thanks for assigning for tempest work, that's definitely a priority right now.<span class=""><br>
<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">
<br>
BTW, how do you think about Ironic-inspector's release model?<br>
You wrote "Version released with Ironic Liberty" as<br>
Ironic-inspector Version 2.1.0 in etherpad [3],<br>
but as you know, Ironic's release model has changed to feature<br>
releases.(right?)<br>
Should we make our release model same as Ironic?<br>
</blockquote>
<br></span>
I guess the whole idea of new release models is NOT to tie projects to each other any more except for The Big Release twice a year :) So I think no, we don't need to. We still can do it, if we have something to release by the time Ironic releases, but I suggest deciding it on case-by-case basis.<br>
<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"><span class="">
<br>
<br>
Best Regards,<br>
Yuiko Takada(Inspector team member)<br>
<br>
2015-06-08 20:38 GMT+09:00 Dmitry Tantsur <<a href="mailto:dtantsur@redhat.com" target="_blank">dtantsur@redhat.com</a><br></span>
<mailto:<a href="mailto:dtantsur@redhat.com" target="_blank">dtantsur@redhat.com</a>>>:<div><div class="h5"><br>
<br>
Hello, Inspector team!<br>
<br>
The renaming process is going pretty well, the last thing we need to<br>
do is to get Infra approval and actual rename [1][2].<br>
<br>
I'd like to allow people (e.g. myself) to start packaging inspector<br>
under it's new name, so I'd like to make 2.0.0 release as soon as<br>
possible (as opposed to scheduling it to particular date). All<br>
breaking changes should land by this release - I don't expect 3.0.0<br>
soon :)<br>
<br>
I've updated our summit etherpad [3] with whatever priorities I<br>
remembered, please have a look. I've also untargeted a few things in<br>
launchpad [4] (and will probably untarget more later on). Please<br>
assign yourself, if you want something done in this release time frame.<br>
<br>
I would like 2.1.0 to be released with Ironic Liberty and be<br>
properly supported.<br>
<br>
Let me know what you think.<br>
<br>
Cheers,<br>
Dmitry<br>
<br>
[1] <a href="https://review.openstack.org/#/c/188030/" target="_blank">https://review.openstack.org/#/c/188030/</a><br>
[2] <a href="https://review.openstack.org/#/c/188798/" target="_blank">https://review.openstack.org/#/c/188798/</a><br>
[3] <a href="https://etherpad.openstack.org/p/liberty-ironic-discoverd" target="_blank">https://etherpad.openstack.org/p/liberty-ironic-discoverd</a><br>
[4] <a href="https://bugs.launchpad.net/ironic-inspector/+milestone/2.0.0" target="_blank">https://bugs.launchpad.net/ironic-inspector/+milestone/2.0.0</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br></div></div>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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><span class=""><br>
<br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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>
<br>
</span></blockquote><div class=""><div class="h5">
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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></div></blockquote></div><br></div></div>