Hi, correct spec link is https://review.openstack.org/#/c/269202/
Spec isn't approved and so FFE isn't granted. It's very important to not spread the team's efforts onto reviewing specs and additional features in the pre-RC time frame, so, I'm considering non-merged spec as a blocker for FFE. Thanks. On Thu, Mar 3, 2016 at 11:08 AM, Akanksha Agrawal <akanksha....@gmail.com> wrote: > Hi folks, > > I would like to request a FFE for the feature “Improving anti-affinity in > Sahara”: > > > BP: https://blueprints.launchpad.net/sahara/+spec/improving-anti-affinity > > > <https://blueprints.launchpad.net/sahara/+spec/improving-anti-affinity> > > Specification Review: https://review.openstack.org/#/c/269202/ > <https://review.openstack.org/#/c/210839/> > > > <https://review.openstack.org/#/c/210839/> > > Code Review: https://review.openstack.org/#/c/282506/ > <https://review.openstack.org/#/c/218638/> > > > Estimated Completion Time: The specification is complete and should not > take more than 1-2 days to be approved. > > The code is under review and needs few more changes before it could be > completed. Mostly pep8 related errors have to be fixed and the error for > backward compatibility has to be thrown. This would not require more than a > week. > > > The Benefits for this change: Improved anti-affinity behaviour while > cluster creation > > > The Risk: The risk would be low for this patch, since the code would be > completed in time. > > > > Thanks, > > Akanksha Agrawal > -- Sincerely yours, Sergey Lukjanov Principal Software Engineer Mirantis Inc.
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
