From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
Cc: stable@dpdk.org, Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-stable] What kind of commits can be backported to help the process
Date: Thu, 16 Feb 2017 13:03:03 +0800 [thread overview]
Message-ID: <20170216050303.GA20916@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <20170215102345.GU23344@autoinstall.dev.6wind.com>
On Wed, Feb 15, 2017 at 11:23:45AM +0100, Nélio Laranjeiro wrote:
> Hi stable mailing list,
>
> As written in the subject, it is not fully clear on what kind of patches
> can enter this branch.
>
> Some fixes apply easily on top of other ones which may not be related,
> the question is on those "unrelated" patches. Is it acceptable to
> backport them, and if yes at what point is it acceptable depending on
> the nature of the patch:
>
> 1. Re-work: just a refactor of some structure, clean-up, ...
> 2. Behavior: it change the behavior of a part of the code, ...
> 3. Performances: it impacts performances (positively or negatively).
> 4. None, the patch must apply by itself.
> 5. ...
>
> What is the expectation for this branch?
Here is the typical flow I took to pick commits to a specific stable
branch:
- firstly, I will get a list of bug fixing commits, with the help of
devtools/git-log-fixes.sh (as well as the "cc: stable@dpdk.org" tag
inside the commit log).
Those commits fix some bugs in a former releases, thus they will be
applied to a specific stable branch.
- Some of them could be applied cleanly. I will then drop a note to
all related people (the author, the reviewer, etc) and stable list,
to inform that this commit will be in a specific stable release.
- And some of them could not be applied cleanly, when conflicts happens
(code base could be changed).
When that happens, I will try to backport it by myself if the commit
is simple enough (say, just few lines of code and the conflicts could
be easily fixed).
If not, I will stop (to not mess something up because I'm not familar
with the code), instead I will then ask the author (and even, the
maintainer) to do the backport. And that's how the 'request-backport'
email comes.
So to answer your question. The backport should be easy (when one guy
knows the code enough). If it invovles re-work and changes the behavior
the commit doesn't have, it basically means it's done wrongly.
That helps?
--yliu
next prev parent reply other threads:[~2017-02-16 5:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 10:23 Nélio Laranjeiro
2017-02-16 5:03 ` Yuanhan Liu [this message]
2017-02-16 8:21 ` Nélio Laranjeiro
2017-02-16 8:42 ` Yuanhan Liu
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=20170216050303.GA20916@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=stable@dpdk.org \
--cc=thomas.monjalon@6wind.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).