[ovirt-devel] [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 status - Go / No Go

Mon Sep 22 11:28:15 UTC 2014

----- Original Message -----
> From: "Yaniv Dary" <ydary at redhat.com>
> To: "Oved Ourfali" <ovedo at redhat.com>
> Cc: Users at ovirt.org, devel at ovirt.org
> Sent: Monday, September 22, 2014 11:07:37 AM
> Subject: Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status - Go / No Go
> 
> 
> 
> ----- Original Message -----
> > From: "Oved Ourfali" <ovedo at redhat.com>
> > To: "Sandro Bonazzola" <sbonazzo at redhat.com>
> > Cc: Users at ovirt.org, devel at ovirt.org
> > Sent: Monday, September 22, 2014 11:03:07 AM
> > Subject: Re: [ovirt-devel] [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0
> > status - Go / No Go
> > 
> > 
> > 
> > ----- Original Message -----
> > > From: "Sandro Bonazzola" <sbonazzo at redhat.com>
> > > To: devel at ovirt.org, Users at ovirt.org
> > > Sent: Monday, September 22, 2014 9:38:13 AM
> > > Subject: [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 status - Go / No
> > > Go
> > > 
> > > Hi,
> > > We are supposed to start composing oVirt 3.5.0 GA (or RC3, depending on
> > > this
> > > morning Go / No go Meeting decisions)
> > > I think we can use this email for discussing / voting 3.5.0 GA release.
> > > Looking at bugzilla status, I vote no go. I also think we should move the
> > > build to Wed allowing maintainers to fix pending blockers.
> > > 
> > > Maintainers:
> > > - Please be sure that 3.5 snapshot satisfy release criteria[9]
> > > - Please be sure that no pending patches are going to block the release
> > > - If any patch must block the GA release please raise the issue as soon
> > > as
> > > possible.
> > > - If any packages need a rebase please raise the issue as soon as
> > > possible.
> > > - Be aware that packages that doesn't need a rebase must be re-built with
> > > final release versioning from the RC2 tag.
> > > 
> > > The bug tracker [1] shows the following proposed blockers to be reviewed:
> > > 
> > > Bug ID	Whiteboard	Status		Summary
> > > 1143042	infra		POST		Repeated error "Failed to create VM external-test"
> > > when
> > > starting new VM
> > > 1143860	infra		POST		Marshaling issue in fencing policy using jsonrpc
> > 
> > I expect both infra issues to be merged by the end of the day.
> > 

Both bugs are now on MODIFIED.

> > > 1142256	integration	NEW		remote engine-reports-setup does not write conf
> > > file
> > > to allow accessing reports from engine
> 
> This is only for 3.5.1.
> 
> > > 1144079	integration	ASSIGNED	local engine-reports-setup does not write
> > > conf
> > > file to allow accessing reports from engine
> 
> This is pending verification from didi.
> 
> 
> > > 
> > > The following bugs are keyworded as Regression and not marked as
> > > blockers[10]
> > > 
> > > Bug ID	Whiteboard	Status	Summary
> > > 1142709	integration	NEW	Trying to deploy hosted-engine via iSCSI device
> > > fails
> > > 1138144	storage		NEW	Failed to autorecover storage domain after
> > > unblocking
> > > connection with host
> > > 1118349	storage		NEW	[vdsm] Creating DataCenter 3.5 using master domain
> > > V1
> > > fails with InquireNotSupportedError
> > > 1138314	virt		NEW	Fail to start vm with payload.
> > > 
> > > 
> > > Feature freeze is now effective, and branch has been created.
> > > All new patches must be backported to 3.5 branch too.
> > > Features completed are marked in green on Features Status Table [2]
> > > 
> > > There are still 77 bugs [3] targeted to 3.5.0.
> > > Excluding node and documentation bugs we still have 53 bugs [4] targeted
> > > to
> > > 3.5.0.
> > > 
> > > More in detail [5]:
> > > 
> > > Whiteboard	NEW	ASSIGNED	POST	Total
> > > docs		13	1		0	14
> > > gluster		8	2		2	12
> > > i18n		0	0		1	1
> > > infra		1	0		3	4
> > > integration	1	2		1	4
> > > node		7	4		0	11
> > > ppc		2	0		4	6
> > > sla		12	0		7	19
> > > virt		3	0		3	6
> > > Total		47	9		21	77
> > > 
> > > 
> > > Maintainers / Assignee:
> > > - Please ensure that completed features are marked in green on Features
> > > Status Table [2]
> > > - If you find a blocker bug please remember to add it to the tracker [1]
> > > - Please fill release notes, the page has been created here [6]
> > > - Please review results from Third Test Day on the etherpad [7] and on
> > > the
> > > mailing lists
> > > - Please update the target to 3.5.1 or later for bugs that won't be in
> > > 3.5.0:
> > >   it will ease gathering the blocking bugs for next releases.
> > > 
> > > Community:
> > > - You're welcome to join us testing last release candidate or nightly
> > > builds
> > > and getting involved in oVirt Quality Assurance[8]
> > > 
> > > [1] http://bugzilla.redhat.com/1073943
> > > [2] http://goo.gl/4SuYdE
> > > [3] http://red.ht/1pVEk7H
> > > [4] http://red.ht/1zT2mSq
> > > [5] http://red.ht/1q7SqNL
> > > [6] http://www.ovirt.org/OVirt_3.5_Release_Notes
> > > [7] http://etherpad.ovirt.org/p/3.5-testday-3
> > > [8] http://www.ovirt.org/OVirt_Quality_Assurance
> > > [9]
> > > http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria_.28WIP.29
> > > [10] http://goo.gl/uavikG
> > > 
> > > Thanks,
> > > 
> > > 
> > > --
> > > Sandro Bonazzola
> > > Better technology. Faster innovation. Powered by community collaboration.
> > > See how it works at redhat.com
> > > _______________________________________________
> > > Users mailing list
> > > Users at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/users
> > > 
> > _______________________________________________
> > Devel mailing list
> > Devel at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> > 
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 