5:50 a.m.
we are about a week away from feature freeze of oVirt 3.3 (May 31st). In
order to be able to converge to this date we would need your help
(feature owners) understanding feature/overall status.
I have updated OVirt 3.3 release-management page [1] with features
status table [2]. having this complete table filled will help us
determine this version readiness.
a test page addition is needed for each feature (link through the table)
- this will enable us good visibility and testing of those features in
test-day.
I have left the old 3.3 feature overview -just below the new table, to
make sure i have taken all needed from that info. please verify all you
need is in the table, since this part will be deleted on feature freeze
readiness review - next Wednesday meeting.
completing filling this table should be done no later than Tuesday May 28th.
Thanks.
[1]http://www.ovirt.org/OVirt_3.3_release-management
[2]http://www.ovirt.org/OVirt_3.3_release-management#Features_Status_Table
[3]http://www.ovirt.org/OVirt_3.3_release-management#Features
6:58 a.m.
On 05/23/2013 06:50 AM, Moran Goldboim wrote:
we are about a week away from feature freeze of oVirt 3.3 (May 31st).
In
order to be able to converge to this date we would need your help
(feature owners) understanding feature/overall status.
I have updated OVirt 3.3 release-management page [1] with features
status table [2]. having this complete table filled will help us
determine this version readiness.
a test page addition is needed for each feature (link through the table)
- this will enable us good visibility and testing of those features in
test-day.
I have left the old 3.3 feature overview -just below the new table, to
make sure i have taken all needed from that info. please verify all you
need is in the table, since this part will be deleted on feature freeze
readiness review - next Wednesday meeting.
completing filling this table should be done no later than Tuesday May
28th.
An example of a testing chart is available on [4]
Mike
[4] http://www.ovirt.org/Features/Node_vdsm_plugin#Testing
Thanks.
[1]http://www.ovirt.org/OVirt_3.3_release-management
[2]http://www.ovirt.org/OVirt_3.3_release-management#Features_Status_Table
[3]http://www.ovirt.org/OVirt_3.3_release-management#Features
_______________________________________________
Arch mailing list
Arch(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/arch
9:01 a.m.
On 05/23/2013 01:50 PM, Moran Goldboim wrote:
we are about a week away from feature freeze of oVirt 3.3 (May 31st).
In order to be able to converge to this date we would need your help
(feature owners) understanding feature/overall status.
I have updated OVirt 3.3 release-management page [1] with features
status table [2]. having this complete table filled will help us
determine this version readiness.
a test page addition is needed for each feature (link through the
table) - this will enable us good visibility and testing of those
features in test-day.
I have left the old 3.3 feature overview -just below the new table, to
make sure i have taken all needed from that info. please verify all
you need is in the table, since this part will be deleted on feature
freeze readiness review - next Wednesday meeting.
completing filling this table should be done no later than Tuesday May
28th.
Thanks.
[1]http://www.ovirt.org/OVirt_3.3_release-management
[2]http://www.ovirt.org/OVirt_3.3_release-management#Features_Status_Table
[3]http://www.ovirt.org/OVirt_3.3_release-management#Features
_______________________________________________
Arch mailing list
Arch(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/arch
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.
Thanks.
2:55 a.m.
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
3984
days inactive
3990
days old
3 comments
3 participants
participants (3)
-
Dave Neary -
Mike Burns -
Moran Goldboim