Considering my current load I expect code to be ready by wednesday March 11th. Maybe we can say that we can grant a FFE as long as the code makes it - in full - by that date? Salvatore On 5 March 2015 at 16:03, Kyle Mestery <mestery at mestery.com> wrote: > On Thu, Mar 5, 2015 at 3:29 AM, Salvatore Orlando <sorlando at nicira.com> > wrote: > >> I was hoping to push code today for [1], but unfortunately I got caught >> by something else during this week and I'll miss the code proposal deadline. >> >> I would like to apply for a FFE; however, since I've experienced FFEs in >> previous release cycles, please treat this request as best-effort if there >> ore other work items with higher priority applying for a FFE. >> >> Thanks for the note Salvatore. I'm fine with granting this an FFE given > it's a good community feature and it's High priority. Do you think you'll > have code pushed out by early next week? Also, lets try to find two core > reviewers who can iterate with you quickly once you do push it so we can > land it fairly fast. > > Thanks, > Kyle > > >> Salvatore >> >> [1] https://blueprints.launchpad.net/neutron/+spec/better-quotas >> >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150305/923441fa/attachment.html>