<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 11/04/2014 09:47 AM, Fabian Deutsch
wrote:<br>
</div>
<blockquote
cite="mid:1118961373.3230464.1415090866162.JavaMail.zimbra@redhat.com"
type="cite">
<pre wrap="">----- Original Message -----
</pre>
<blockquote type="cite">
<pre wrap="">On Sun, Sep 14, 2014 at 03:17:39PM +0300, Itamar Heim wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 09/12/2014 03:22 PM, Itamar Heim wrote:
</pre>
<blockquote type="cite">
<pre wrap="">With oVirt 3.5 nearing GA, time to ask for "what do you want to see in
oVirt 3.6"?
</pre>
</blockquote>
<pre wrap="">
Even the short list of items mentions so far are big features we would need
to do justice with.
this means probably a slightly longer cycle than the 6 months we currently
do.
</pre>
</blockquote>
<pre wrap="">
We're not so good in keeping up with deadlines - our recent 3.5 version
slipped for 2.5 months past the original plan. With longer cycles, this
is even harder to control.
Can we instead break the "heavier" features to smaller phases, that are
easier to maintain, and deliver the complete feature in 3.7?
</pre>
</blockquote>
<pre wrap="">
Hey,
yep, I think this is a good idea to get control over the big features.
- fabian</pre>
</blockquote>
This reminds me a lot of Intel's "tick-tock" method that I've grown
quite fond of over the years.<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<img src="cid:part1.06090004.00080408@netbulae.eu"><br>
<br>
Lay the groundwork in one version and than finish with the next.<br>
<br>
For oVirt this could mean for example we implement new things in
vdsm in 3.6 and they can be tested if you want to, then in 3.7 they
can be polished off (and some bugs fixed) and exposed in the GUI.<br>
<br>
Kind regards,<br>
<br>
Jorick<br>
<br>
<blockquote
cite="mid:1118961373.3230464.1415090866162.JavaMail.zimbra@redhat.com"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">with many of the features requiring way newer versions of some of the
components, I think we should plan for "3.6 cluster" to require an .el7
host
(expecting even 7.1 to be out before we release oVirt 3.6).
so i want us to plan for:
- oVirt 3.6 supports .el6 and .el7 hosts in 3.5 cluster (and for fedora
- fc20?)
- oVirt 3.6 supports .el7 in 3.6 cluster (and for fedora - fc21?)
</pre>
</blockquote>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
<BR />
<BR />
<b style="color:#604c78"></b><br><span style="color:#604c78;"><font color="000000"><span style="mso-fareast-language:en-gb;" lang="NL">Met vriendelijke groet, With kind regards,<br><br></span>Jorick Astrego</font></span><b style="color:#604c78"><br><br>Netbulae Virtualization Experts </b><br><hr style="border:none;border-top:1px solid #ccc;"><table style="width: 522px"><tbody><tr><td style="width: 130px;font-size: 10px">Tel: 053 20 30 270</td> <td style="width: 130px;font-size: 10px">info@netbulae.eu</td> <td style="width: 130px;font-size: 10px">Staalsteden 4-3A</td> <td style="width: 130px;font-size: 10px">KvK 08198180</td></tr><tr> <td style="width: 130px;font-size: 10px">Fax: 053 20 30 271</td> <td style="width: 130px;font-size: 10px">www.netbulae.eu</td> <td style="width: 130px;font-size: 10px">7547 TA Enschede</td> <td style="width: 130px;font-size: 10px">BTW NL821234584B01</td></tr></tbody></table><br><hr style="border:none;border-top:1px solid #ccc;"><BR />
</body>
</html>