[3.3 release process] feature freeze readiness

[Dave Neary]

Hi,

On 05/28/2013 04:01 PM, Moran Goldboim wrote:
> Thanks for everyone who updated their status on the table.
> Still there are missing features around virt, infra, storage and sla,
> please complete statuses on this missing features today so we can attend
> to understand the release status tomorrow's meeting.

The features still missing a status and owner are:

* GlusterFS Storage Domain
* Allow resign/force re-election of SPM

Also, a number of features have not set a release priority - especially
for red and orange features, we need to know whether the feature is
considered "must"/"should"/"optional" for 3.3, because those are the
ones that will end up delaying a release.

* RAM snapshots
* noVNC console
* Non Plugin RDP Invocation
* Instance Types

After that, we can start looking at red flag features to help set the
release date.

A few things jumped out at me:

== Red features marked as Must

For each of these, we need an estimate of how long the feature will take
to complete - these will almost certainly delay the release.

* Multiple Gateways
* Edit Connection Properties
* oVirt scheduler
* Scheduling API
* Networking QoS

Next priority is the orange musts - one in particular jumps out at me:
"Watchdog engine support" has a comment "REST API missing" - which
sounds ominous.

Thanks to everyone for filling this out! And thanks to Moran for taking
the lead on this, it's very useful.

Cheers,
Dave.
-- 
Dave Neary - Community Action and Impact
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13