Michael Still wrote:
> We're soon to hit feature freeze, as discussed in Thierry's recent
> email. I'd like to outline the process for requesting a freeze
> exception:
>     * your code must already be up for review
>     * your blueprint must have an approved spec
>     * you need three (3) sponsoring cores for an exception to be granted
>     * exceptions must be granted before midnight, Friday this week
> (September 5) UTC
>     * the exception is valid until midnight Friday next week
> (September 12) UTC when all exceptions expire
> For reference, our rc1 drops on approximately 25 September, so the
> exception period needs to be short to maximise stabilization time.
> John Garbutt and I will both be granting exceptions, to maximise our
> timezone coverage. We will grant exceptions as they come in and gather
> the required number of cores, although I have also carved some time
> out in the nova IRC meeting this week for people to discuss specific
> exception requests.

I'd like to add that every exception approved adds up to create moving
parts at a moment where we want to slow down to let QA and Docs and
other downstream stakeholders catch up.

Obviously, things that are already approved and working their way
through the gate should be in early enough to limit this disruption. But
in general, targeting more than 25% of your juno-3 velocity to -rc1 is a
bit unreasonable. For Nova, that means that more than 7 exceptions is
starting to be a stability issue.

Please keep that in mind every time you go to support a FFE.

Thierry Carrez (ttx)

OpenStack-dev mailing list

Reply via email to