<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 03/15/2012 07:25 PM, Ofer Schreiber wrote:
<blockquote
cite="mid:af032398-dc67-400b-809b-d2d798daa111@zmail14.collab.prod.int.phx2.redhat.com"
type="cite">
<pre wrap="">All,
The final draft of the release process is available at <a class="moz-txt-link-freetext" href="http://www.ovirt.org/wiki/Release_Process">http://www.ovirt.org/wiki/Release_Process</a>
As discussed in the last sync meeting, this draft includes a formal release vote procedure, described in <a class="moz-txt-link-freetext" href="http://www.ovirt.org/governance/voting/">http://www.ovirt.org/governance/voting/</a>
Comment now, or forever hold your peace.
Thanks,
Ofer Schreiber
oVirt Release Manager
_______________________________________________
Arch mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Arch@ovirt.org">Arch@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/arch">http://lists.ovirt.org/mailman/listinfo/arch</a>
</pre>
</blockquote>
looks good to me, please consider the following,<b></b><big><br>
</big>
<pre wrap=""><big><a class="moz-txt-link-freetext" href="http://www.ovirt.org/wiki/Release_Process">http://www.ovirt.org/wiki/Release_Process</a></big></pre>
[snip]<br>
6. 30 days before release - release candidate<br>
* OPTIONAL: final release requires three +1 from community
members<br>
<br>
i would like to see +1 from each component dev owner- indicating
that his component is ready for final release.<br>
in addition i think we need to set musts and shoulds for components
as well, which will indicate which components are a must for a
release, thus indicating if the release should be delayed based on a
major problem on a specific component.<br>
<br>
Moran.<br>
</body>
</html>