From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org, dev@dpdk.org, techboard@dpdk.org, bluca@debian.org,
yliu@fridaylinux.org, ktraynor@redhat.com,
christian.ehrhardt@canonical.com, yskoh@mellanox.com
Subject: Re: [dpdk-web] [PATCH v2] update stable releases roadmap
Date: Wed, 18 Apr 2018 13:28:00 +0100 [thread overview]
Message-ID: <b8d413f2-e316-8a5e-564b-f990a070f7bd@intel.com> (raw)
In-Reply-To: <2746771.jHPYkc9GPR@xps>
On 4/18/2018 10:14 AM, Thomas Monjalon wrote:
> 18/04/2018 11:05, Ferruh Yigit:
>> On 4/11/2018 12:28 AM, Thomas Monjalon wrote:
>>> - <p>Typically a new stable release version follows a mainline release
>>> - by 1-2 weeks, depending on the test results.
>>> + <p>The first stable release (.1) of a branch should follow
>>> + its mainline release (.0) by at least two months,
>>> + after the first release candidate (-rc1) of the next branch.
>>
>> Hi Thomas,
>>
>> What this change suggest? To be able to backport patches from rc1?
>
> Yes, it is the proposal we discussed earlier.
> We can wait one week after RC1 to get some validation confirmation.
> Do you agree?
This has been discussed in tech-board, what I remember the decision was to wait
the release to backport patches into stable tree.
next prev parent reply other threads:[~2018-04-18 12:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180309133612.19927-1-thomas@monjalon.net>
2018-04-10 23:28 ` [PATCH v2] update stable releases roadmap Thomas Monjalon
2018-04-11 10:04 ` Luca Boccassi
2018-04-11 10:43 ` Christian Ehrhardt
2018-04-11 15:10 ` Kevin Traynor
2018-04-18 9:05 ` [dpdk-web] " Ferruh Yigit
2018-04-18 9:14 ` Thomas Monjalon
2018-04-18 12:28 ` Ferruh Yigit [this message]
2018-04-18 13:28 ` Thomas Monjalon
2018-04-19 9:38 ` Kevin Traynor
2018-04-20 15:52 ` Aaron Conole
2018-04-25 8:33 ` Ferruh Yigit
2018-04-25 10:03 ` Luca Boccassi
2018-04-30 10:47 ` Thomas Monjalon
2018-05-01 14:16 ` Aaron Conole
2018-05-01 15:46 ` Kevin Traynor
2018-05-01 16:02 ` Thomas Monjalon
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=b8d413f2-e316-8a5e-564b-f990a070f7bd@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
--cc=yliu@fridaylinux.org \
--cc=yskoh@mellanox.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 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.