From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <richard.purdie@linuxfoundation.org>
Received: from dan.rpsys.net (dan.rpsys.net [93.97.175.187])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id C96A1E007C7
	for <toaster@yoctoproject.org>; Thu, 30 Jan 2014 02:42:46 -0800 (PST)
Received: from localhost (dan.rpsys.net [127.0.0.1])
	by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu4) with ESMTP id
	s0UAgF4r031031; Thu, 30 Jan 2014 10:42:16 GMT
X-Virus-Scanned: Debian amavisd-new at dan.rpsys.net
Received: from dan.rpsys.net ([127.0.0.1])
	by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id ftwZ_oLt6jxV; Thu, 30 Jan 2014 10:42:15 +0000 (GMT)
Received: from [192.168.3.10] (rpvlan0 [192.168.3.10]) (authenticated bits=0)
	by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu1) with ESMTP id
	s0UAg916031026
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 30 Jan 2014 10:42:11 GMT
Message-ID: <1391078523.24655.187.camel@ted>
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>
Date: Thu, 30 Jan 2014 10:42:03 +0000
In-Reply-To: <CF0FD740.3BE60%belen.barros.pena@intel.com>
References: <011977994B5AE74ABA2BD08E983BAAABA2F84986@ALA-MBA.corp.ad.wrs.com>
	<CF0FD740.3BE60%belen.barros.pena@intel.com>
X-Mailer: Evolution 3.8.4-0ubuntu1 
Mime-Version: 1.0
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>, "Zhang,
	Jessica" <jessica.zhang@intel.com>,
	"'toaster@yoctoproject.org'" <toaster@yoctoproject.org>
Subject: Re: Unable to rebase
X-BeenThere: toaster@yoctoproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Web based interface for BitBake <toaster.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/toaster>,
	<mailto:toaster-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/toaster>
List-Post: <mailto:toaster@yoctoproject.org>
List-Help: <mailto:toaster-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/toaster>,
	<mailto:toaster-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 10:42:47 -0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Thu, 2014-01-30 at 10:23 +0000, Barros Pena, Belen wrote:
> I'll try to speed up the review process. The problem I have is that, in my
> experience, it pays off to fix as many issues as possible before merging
> to a master branch (toaster/master in our case). The moment code is merged
> to master, it seems to become necessary to raise issues using the bug
> tracking system, which results in the number of issues ballooning up. I
> don't have a problem with that, but people having to fix the issues might
> find it difficult to decide what to do first: fixing problems from
> previous features or tackling new features.
> 
> I am copying everybody because this is very much a process problem: it
> would be good to hear what everybody else thinks.

FWIW, my take on this is that:

There is no hard requirement to have a bug open against an issue in
master. In particular, if you find an issue and have a fix which gets
sent out quickly, there is no point in taking the process overhead of
opening the bug only to close it again.

Equally, if there is a bug found in master and you don't have an
immediate fix, we do prefer to open bugs to ensure the issue does not
get forgotten about.

Cheers,

Richard