<div dir="ltr"><div>I'll leave to Kevin's more informed judgment to comment on whether it is appropriate to merge:</div><div><br></div><div>[1] is a list of patches still under review on the feature branch. Some of them fix issues (like executing API actions), or implement TODOs</div><div><br></div><div>This is the current list of TODOs:</div><div><div>salvatore@ubuntu:/opt/stack/neutron$ find ./neutron/newapi/ -name \*.py | xargs grep -n "TODO"</div><div>./neutron/newapi/hooks/context.py:50: # TODO(kevinbenton): is_admin logic</div><div>./neutron/newapi/hooks/notifier.py:22: # TODO(kevinbenton): implement</div><div>./neutron/newapi/hooks/member_action.py:28: # TODO(salv-orlando): This hook must go. Handling actions like this is</div><div>./neutron/newapi/hooks/quota_enforcement.py:33: # TODO(salv-orlando): This hook must go when adaptin the pecan code to</div><div>./neutron/newapi/hooks/attribute_population.py:59: # TODO(kevinbenton): the parent_id logic currently in base.py</div><div>./neutron/newapi/hooks/ownership_validation.py:34: # TODO(salvatore-orlando): consider whether this check can be folded</div><div>./neutron/newapi/app.py:40: #TODO(kevinbenton): error templates</div><div>./neutron/newapi/controllers/root.py:150: # TODO(kevinbenton): allow fields after policy enforced fields present</div><div>./neutron/newapi/controllers/root.py:160: # TODO(kevinbenton): bulk!</div><div>./neutron/newapi/controllers/root.py:190: # TODO(kevinbenton): bulk?</div><div>./neutron/newapi/controllers/root.py:197: # TODO(kevinbenton): bulk?</div></div><div><br></div><div>In my opinion the pecan API now is "working-ish"; however we know it is not yet 100% functionally equivalent; but most importantly we don't know how it works. So far a few corners have bet cut when it comes to testing.</div><div>Even if "it works" it is therefore probably usable. Unfortunately I don't know what are the criteria the core team evaluates for merging it back (and I'm sure that for this release at least the home grown WSGI won't be replaced).</div><div><br></div><div>Salvatore</div><div><br></div>[1] <a href="https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:feature/pecan,n,z">https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:feature/pecan,n,z</a><br></div><div class="gmail_extra"><br><div class="gmail_quote">On 28 August 2015 at 22:51, Kyle Mestery <span dir="ltr"><<a href="mailto:mestery@mestery.com" target="_blank">mestery@mestery.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"><div><div><div><div>Folks:<br><br></div>Kevin wants to merge the pecan stuff, and I agree with him. I'm on vacation next week during Liberty-3, so Armando, Carl and Doug are running the show while I'm out. I would guess that if Kevin thinks it's ok to merge it in before Liberty-3, I'd go with his opinion and let it happen. If not, it can get an FFE and we can do it post Liberty-3.<br><br></div>I'm sending this to the broader openstack-dev list so that everyone can be aware of this plan, and so that Ihar can help collapse things back next week with Doug on this.<br><br></div>Thanks!<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888">Kyle<br></font></span></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>