Open Stack

Stephen Gran wrote:
> I sent a mail a month ago about adding a tags API to the EC2 API, and
> the consensus at the time was to do it by using the native API rather
> than creating a bespoke EC2 solution.  Unfortunately, work pulled me in
> other directions for a bit, but I've got it on review now:
> https://review.openstack.org/#/c/23256/
> https://review.openstack.org/#/c/23258/
> 
> I realize these are arriving late, but we find this ability incredibly
> useful.  They are minimally intrusive, so hopefully you'll find them
> acceptable.

I could find them acceptable if I saw them coming. There is a reason why
we go through the hassle of targeting blueprints and tracking milestone
and series goals: so that we know what's coming and can keep current on
the amount of disruption that will affect final release quality. A
number of exceptions were granted at Feature Freeze point two weeks ago,
based on that picture.

At this point, feature stuff that was not on the Grizzly roadmap in the
last months is *very* unlikely to get an exception. We need to stop
adding features and expanding scope to let everyone concentrate on
bugfixing and reaching an acceptable level of quality before we release
on April 4.

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack