From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>
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
Date: Thu, 30 Jan 2014 10:42:03 +0000 [thread overview]
Message-ID: <1391078523.24655.187.camel@ted> (raw)
In-Reply-To: <CF0FD740.3BE60%belen.barros.pena@intel.com>
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
next prev parent reply other threads:[~2014-01-30 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <011977994B5AE74ABA2BD08E983BAAABA2F84986@ALA-MBA.corp.ad.wrs.com>
2014-01-30 10:23 ` Unable to rebase Barros Pena, Belen
2014-01-30 10:42 ` Richard Purdie [this message]
2014-01-30 11:23 ` Barros Pena, Belen
2014-01-30 10:44 ` Damian, Alexandru
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1391078523.24655.187.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=belen.barros.pena@intel.com \
--cc=jessica.zhang@intel.com \
--cc=paul.eggleton@linux.intel.com \
--cc=toaster@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.