On 20/08/2012, at 10:02 PM, Mike Burns wrote:
> Hi all,
> 
> Now that oVirt 3.1 has shipped, we need to start the planning process
> for the next release.  One of the major topics for this week's weekly
> sync is to review the release criteria.  
> 
> The criteria we used for 3.1 is laid out on the wiki [1].  I will be
> posting an equivalent version for the next release in the next couple
> days, but it will mostly be copy/paste from this page.  
> 
> Please think about release criteria and whether or not we want to
> add/remove/change things for this release.  This needs to be determined
> now to make sure that the release process runs smoother down the line.

Is there some way we can do an end-to-end platform test for most
of the things mentioned there, to sanity check the binaries before
announcement?

Trying to think of some way to catch the "broken ISO" problem that 3.1
has with NFS storage.  So, something similar doesn't occur again in
future.

Any ideas?

Regards and best wishes,

Justin Clift

> Thanks
> 
> Mike
> 
> [1] http://wiki.ovirt.org/wiki/Second_Release
> 
> 
> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

--
Aeolus Community Manager
http://www.aeolusproject.org

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to