On Fri, Aug 26, 2016 at 7:14 PM, Steven Hardy <shardy@xxxxxxxxxx> wrote:
There have been some discussions on $subject recently, so I wanted to
a status update.
Next week we will tag our newton-3 release, and we're currently working
either land or defer the remaining features tracked here:
We need to land as many of the "Needs Code Review" features as we can
before cutting the release next week, so please help by prioritizing
After newton-3 is released, we'll have reached Feature Freeze for
and any features landed after this point must be agreed as feature
exceptions (everything else will be deferred to Ocata) - the process is
mail this list with a justification, and details of which patches need
land, then we'll reach consensus over if it will be accepted or not
on the level of risk, and the status of the patches.
Currently there are three potential FFEs which I'm aware of:
1. Mistral API
We've made good progress on this over recent weeks, but several patches
remain - this is the umbrella BP, and it links several dependent BPs
are mostly posted but need code reviews, please help by testing and
2. Composable Roles
There are two parts to this, some remaining cleanups related to
configuration (such as bind_ip's) which need to land, and the related
Some patches still need to be fixed or written to enable custom-roles -
it's a stretch but I'd say a FFE may be reasonable provided we can get
remaining patches functional in the next few days (I'm planning to do
3. Contrail integration
There are patches posted for this, but they need work - Carlos is
so I'd suggest it should be possible to land these as a FFE (should be
risk as it's all disabled by default)
These are the main features I'm aware of that are targetted to newton-3
but will probably slip, are there others folks want to raise?
Well,Â https://review.openstack.org/#/c/282307/ is still in progress and
will need an FFE. What's the official process to apply for the exception?