<p dir="ltr"><br>
On May 6, 2015 4:47 AM, "Martin Perina" <<a href="mailto:mperina@redhat.com">mperina@redhat.com</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> IMO we should add a warning to release notes that oVirt 3.6 Alpha requires<br>
> OpenJDK 1.7 for engine and it will not work with OpenJDK 1.8 (even though<br>
> our current packaging requirements allows OpenJDK 1.8).</p>
<p dir="ltr">Why is it not considered a bug that our packaging requirements allow a version of OpenJDK that we know will not work? Fixing the package requirements to exclude 1.8 would go a long way toward preventing failed installations (or make failures more obvious).</p>
<p dir="ltr">Is there a bug open to track fixing oVirt to work with OpenJDK 1.8?</p>
<p dir="ltr">-Bob</p>
<p dir="ltr">><br>
> Thanks<br>
><br>
> Martin<br>
><br>
> ----- Original Message -----<br>
> > From: "Sandro Bonazzola" <<a href="mailto:sbonazzo@redhat.com">sbonazzo@redhat.com</a>><br>
> > To: <a href="mailto:devel@ovirt.org">devel@ovirt.org</a>, <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> > Sent: Monday, May 4, 2015 1:26:07 PM<br>
> > Subject: [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week<br>
> ><br>
> > Hi,<br>
> > just a quick reminder that oVirt 3.6.0 Alpha is scheduled for May 6th[1].<br>
> ><br>
> ><br>
> > ACTION: Maintainers, please check Alpha Release Criteria[2] to ensure we can<br>
> > release this Alpha on Wednesday.<br>
> > MUST: All sources must be available on <a href="http://ovirt.org">ovirt.org</a><br>
> > MUST: All packages listed by subprojects must be available in the<br>
> > repository<br>
> > MUST: All accepted features must be substantially complete and in a<br>
> > testable state and enabled by default -- if so specified by the change<br>
> ><br>
> > About this last "MUST" I think that we should drop it having changed the<br>
> > release process after release criteria discussion and move it to beta<br>
> > release<br>
> > criteria.<br>
> ><br>
> > VOTE: please ack for moving "MUST: All accepted features must be<br>
> > substantially complete and in a testable state and enabled by default -- if<br>
> > so<br>
> > specified by the change" to beta release criteria<br>
> ><br>
> > ACTION: Maintainers: please send a list of the packages provided by your<br>
> > sub-project.<br>
> > If no list will be provided, the list will be taken by the jenkins nightly<br>
> > publisher job[3] used for publishing ovirt-master-snapshot.<br>
> ><br>
> > ACTION: Maintainers and QE: please fill the Test Day wiki page[4]<br>
> ><br>
> ><br>
> > [1] <a href="http://www.ovirt.org/OVirt_3.6_Release_Management#Key_Milestones">http://www.ovirt.org/OVirt_3.6_Release_Management#Key_Milestones</a><br>
> > [2] <a href="http://www.ovirt.org/OVirt_3.6_Release_Management#Alpha_Release_Criteria">http://www.ovirt.org/OVirt_3.6_Release_Management#Alpha_Release_Criteria</a><br>
> > [3]<br>
> > <a href="http://jenkins.ovirt.org/view/Publishers/job/publish_ovirt_rpms_nightly_master/">http://jenkins.ovirt.org/view/Publishers/job/publish_ovirt_rpms_nightly_master/</a><br>
> > [4] <a href="http://www.ovirt.org/OVirt_3.6_Test_Day">http://www.ovirt.org/OVirt_3.6_Test_Day</a><br>
> ><br>
> ><br>
> > --<br>
> > Sandro Bonazzola<br>
> > Better technology. Faster innovation. Powered by community collaboration.<br>
> > See how it works at <a href="http://redhat.com">redhat.com</a><br>
> > _______________________________________________<br>
> > Devel mailing list<br>
> > <a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
> > <a href="http://lists.ovirt.org/mailman/listinfo/devel">http://lists.ovirt.org/mailman/listinfo/devel</a><br>
> ><br>
> _______________________________________________<br>
> Devel mailing list<br>
> <a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/devel">http://lists.ovirt.org/mailman/listinfo/devel</a><br>
</p>