[ovirt-devel] Reminder: [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.6.0 status - release criteria

[Eyal Edri]

i didn't see any date for stable branch creation, or it's called by a different name?
also, worth maybe doing an internal discussion on ovirt vs rhev 3.6 release, in terms of milestones, qe verification on upstream, etc...

e.

----- Original Message -----
> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
> To: devel at ovirt.org
> Cc: "Juan Hernandez" <jhernand at redhat.com>, "Barak Azulay" <bazulay at redhat.com>, "Yaniv Dary" <ydary at redhat.com>,
> "Einav Cohen" <ecohen at redhat.com>, "Dan Kenigsberg" <danken at redhat.com>, "Fabian Deutsch" <fabiand at redhat.com>,
> "Yaniv Bronheim" <ybronhei at redhat.com>, "Martin Sivak" <msivak at redhat.com>, "Tomas Jelinek" <tjelinek at redhat.com>,
> "Adam Litke" <alitke at redhat.com>, "Itamar Heim" <iheim at redhat.com>, "Doron Fediuck" <dfediuck at redhat.com>, "Eyal
> Edri" <eedri at redhat.com>, "David Caro" <dcaroest at redhat.com>, "Oved Ourfalli" <ovedo at redhat.com>, "Lior Vernia"
> <lvernia at redhat.com>, "Allon Mureinik" <amureini at redhat.com>, "Michal Skrivanek" <mskrivan at redhat.com>, "Gil Klein"
> <gklein at redhat.com>
> Sent: Tuesday, October 28, 2014 12:02:00 PM
> Subject: Reminder: [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.6.0 status - release criteria
> 
> Hi,
> since I don't see activity on this, just a gentle reminder that we should
> close release criteria discussion for 2014-11-12.
> Is everybody happy just with what was proposed
> here: http://lists.ovirt.org/pipermail/devel/2014-September/008695.html
> and here: http://lists.ovirt.org/pipermail/users/2014-October/028451.html
> ?
> 
> 
> Il 22/10/2014 09:21, Sandro Bonazzola ha scritto:
> > Hi,
> > according to oVirt Release Process [1], a week after the n-1 release is
> > out, a release criteria for the new release should be discussed.
> > 
> > Release criteria will include MUST items and SHOULD items (held in wiki)
> >     MUST items will DELAY the release in any case.
> >     SHOULD items will include less critical flows and new features.
> >     SHOULD items will be handled as "best-effort" by component owners
> > Component owners (e.g. Node, engine-core, vdsm) must ACK the criteria
> > suggested.
> > Release criteria discussions shouldn't take more then 2 weeks
> > Progress on MUST items should be review every month, during the weekly
> > meeting
> > 
> > This means that starting today, we should define release criteria for
> > November 12th.
> > A couple of email have been already posted about this:
> > 
> > * LINK: http://lists.ovirt.org/pipermail/devel/2014-August/008533.html
> > * LINK: http://lists.ovirt.org/pipermail/devel/2014-September/008695.html
> > 
> > as starting point for the discussion.
> > 
> > Release management for 3.6.0 has been created [2]
> > The key milestones for this release must be scheduled:
> > 
> > Key Milestones
> >     Release criteria discussion start: 2014-10-22
> >     Release criteria ready: 2014-11-12
> >     Feature freeze: 60 Days before release
> >     First Test Day: 45 days before release
> >     Release Candidate: 30 days before release
> >     Release: 6 months after oVirt 3.5.0 release
> > 
> > A tracker bug for 3.6.0 has been created [3] and currently show no
> > blockers.
> > 
> > There are 384 bugs [4] targeted to 3.6.0.
> > Excluding node and documentation bugs we have 364 bugs [5] targeted to
> > 3.6.0.
> > 
> > [1] http://www.ovirt.org/Release_process
> > [2] http://www.ovirt.org/OVirt_3.6_Release_Management
> > [3] https://bugzilla.redhat.com/show_bug.cgi?id=1155425
> > [4] http://goo.gl/zwkF3r
> > [5] http://goo.gl/ZbUiMc
> > 
> 
> 
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>