From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Dennis Lan (dlan)" <dennis.yxun@gmail.com>, xen-devel@lists.xen.org
Subject: Re: which branch should I tracking, stable or staging?
Date: Tue, 29 Apr 2014 00:29:45 +0100 [thread overview]
Message-ID: <535EE469.4030007@citrix.com> (raw)
In-Reply-To: <CAF1ZMEfB0SwpauT2TYbhxqa=Xij3pL0ZXC1=JsDpMwzTx_54dw@mail.gmail.com>
On 28/04/2014 22:37, Dennis Lan (dlan) wrote:
> HI ALL:
> I'm usually tracking *stable* branch (eg. remotes/origin/stable-4.3)
> for security bugs and critical fixes. but I noticed that a few
> patches/fixes for branch-4.4 are not going into stable
> branch(remotes/origin/stable-4.4), including XSA-93,94(most of them
> for arm ARCH).
> So my question: any reason why those commits doesn't merge into
> stable branch? or should I tracking staging branch instead? because
> those commits in staging branch will eventually goes into stable
> branch, or will any of these commits may get reverted by chance?
>
> Lan
If you notice, XSAs 93 and 94 are in staging-4.4 pending successful pass
of the OSS test to be merged. OSS test is currently undergoing some
difficulties which is why they have not yet been merged.
As far as stable branches go, bugfixes do gradually happen as and when
the maintainers choose, although there is usually a collection period or
two before dot-releases where suggestions are requested.
~Andrew
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-04-28 23:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 21:37 which branch should I tracking, stable or staging? Dennis Lan (dlan)
2014-04-28 23:29 ` Andrew Cooper [this message]
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=535EE469.4030007@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=dennis.yxun@gmail.com \
--cc=xen-devel@lists.xen.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 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).