[ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week

[Martin Perina]

----- Original Message -----
> From: "Bob Doolittle" <bob at doolittle.us.com>
> To: "Martin Perina" <mperina at redhat.com>
> Cc: devel at ovirt.org, "Sandro Bonazzola" <sbonazzo at redhat.com>, Users at ovirt.org
> Sent: Wednesday, May 6, 2015 1:33:03 PM
> Subject: Re: [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
> 
> On May 6, 2015 4:47 AM, "Martin Perina" <mperina at redhat.com> wrote:
> >
> > Hi,
> >
> > IMO we should add a warning to release notes that oVirt 3.6 Alpha requires
> > OpenJDK 1.7 for engine and it will not work with OpenJDK 1.8 (even though
> > our current packaging requirements allows OpenJDK 1.8).
> 
> 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).
> 
> Is there a bug open to track fixing oVirt to work with OpenJDK 1.8?

When we will move to WildFly [1], we could use also OpenJDK 1.8, but not before.

Martin

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1121327

> 
> -Bob
> 
> >
> > Thanks
> >
> > Martin
> >
> > ----- Original Message -----
> > > From: "Sandro Bonazzola" <sbonazzo at redhat.com>
> > > To: devel at ovirt.org, Users at ovirt.org
> > > Sent: Monday, May 4, 2015 1:26:07 PM
> > > Subject: [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha
> release  this week
> > >
> > > Hi,
> > > just a quick reminder that oVirt 3.6.0 Alpha is scheduled for May
> 6th[1].
> > >
> > >
> > > ACTION: Maintainers, please check Alpha Release Criteria[2] to ensure
> we can
> > > release this Alpha on Wednesday.
> > >     MUST: All sources must be available on ovirt.org
> > >     MUST: All packages listed by subprojects must be available in the
> > >     repository
> > >     MUST: All accepted features must be substantially complete and in a
> > >     testable state and enabled by default -- if so specified by the
> change
> > >
> > > About this last "MUST" I think that we should drop it having changed the
> > > release process after release criteria discussion and move it to beta
> > > release
> > > criteria.
> > >
> > > VOTE: please ack for moving "MUST: All accepted features must be
> > > substantially complete and in a testable state and enabled by default
> -- if
> > > so
> > > specified by the change" to beta release criteria
> > >
> > > ACTION: Maintainers: please send a list of the packages provided by your
> > > sub-project.
> > > If no list will be provided, the list will be taken by the jenkins
> nightly
> > > publisher job[3] used for publishing ovirt-master-snapshot.
> > >
> > > ACTION: Maintainers and QE: please fill the Test Day wiki page[4]
> > >
> > >
> > > [1] http://www.ovirt.org/OVirt_3.6_Release_Management#Key_Milestones
> > > [2]
> http://www.ovirt.org/OVirt_3.6_Release_Management#Alpha_Release_Criteria
> > > [3]
> > >
> http://jenkins.ovirt.org/view/Publishers/job/publish_ovirt_rpms_nightly_master/
> > > [4] http://www.ovirt.org/OVirt_3.6_Test_Day
> > >
> > >
> > > --
> > > Sandro Bonazzola
> > > Better technology. Faster innovation. Powered by community
> collaboration.
> > > See how it works at redhat.com
> > > _______________________________________________
> > > Devel mailing list
> > > Devel at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/devel
> > >
> > _______________________________________________
> > Devel mailing list
> > Devel at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
>