On 07/16/2013 04:36 PM, Omer Frenkel wrote:

----- Original Message -----
From: "Itamar Heim" <[email protected]>
To: "Moran Goldboim" <[email protected]>, "Doron Fediuck" <[email protected]>, 
"Greg Padgett"
<[email protected]>, "Omer Frenkel" <[email protected]>, "Michal Skrivanek" 
<[email protected]>, "Mike
Kolesnik" <[email protected]>, "Livnat Peer" <[email protected]>, "Ayal Baron" 
<[email protected]>, "Federico
Simoncelli" <[email protected]>
Cc: "engine-devel" <[email protected]>
Sent: Tuesday, July 16, 2013 4:03:46 PM
Subject: Re: [Engine-devel] oVirt 3.3 feature freeze and delivery to testing 
repo

On 07/15/2013 05:45 PM, Moran Goldboim wrote:
Maintainers and all,

due to some misunderstanding regarding feature freeze for ovirt 3.3
release (suppose to be today, but marked as Jul 17th on release page),
we are extending feature freeze till wendesday.

feature owners:
-please update 3.3 release page [1] with the feature status
-please update testing page for your feature

package owners- once your component is ready (should be done till
wendesday)
-tag your repo for 3.3 beta release
-provide srpm to mike
-provide fc19/el6 rpms builds using mock to mike

mike if you would like to set a place people can upload it too please
let us know.


[1]http://www.ovirt.org/OVirt_3.3_release-management#Features_Status_Table

what's the status of these which seem a shame to release without (and
all are supposed to be on their final step)?
- glance integration (federico)
- Neutron (quantum) integration (livnat/mike)?
- cloud-init (greg/omer)?
pending ack from REST

- plugable scheduling (doron)?

Thanks,
     Itamar


Adding Mike.
Guys - please be ready to update the status of those features on weekly meeting today. My feeling that if those features aren't in we should block the alpha/beta1 release of the version which will go also to test-day till those are merged.

Thanks.
_______________________________________________
Engine-devel mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/engine-devel

Reply via email to