From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: Luca Boccassi <bluca@debian.org>, "web@dpdk.org" <web@dpdk.org>,
"yliu@fridaylinux.org" <yliu@fridaylinux.org>,
"ktraynor@redhat.com" <ktraynor@redhat.com>,
"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-web] [dpdk-techboard] [PATCH] update stable releases roadmap
Date: Fri, 9 Mar 2018 15:24:01 +0000 [thread overview]
Message-ID: <d0930c39-b522-9cf9-7191-c08d67ca5117@intel.com> (raw)
In-Reply-To: <138268661.yuZPGn2xFY@xps>
On 3/9/2018 2:19 PM, Thomas Monjalon wrote:
> 09/03/2018 15:03, Ananyev, Konstantin:
>> From: Thomas Monjalon
>>> 09/03/2018 14:44, Luca Boccassi:
>>>> On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote:
>>>>> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>>>>>
>>>>> ---
>>>>> This is at the same time, a call for volunteer,
>>>>> and a proposed change to shorten the wait for the first stable
>>>>> releases
>>>>> from at least 3 months to 2 months.
>>>>>
>>>>> Let's add this discussion to the agenda of the next techboard
>>>>> meeting.
>>>>
>>>> The issue is how to decide what goes into a stable release, if it does
>>>> not follow a main release.
>>>>
>>>> Right now we follow the main release as that means there is a list of
>>>> accepted and merged commits that can be backported - if the stable
>>>> release is anticipated, what is going to be backported?
>>>
>>> If we pull patches more regularly in master, there can be a lot of fixes
>>> accumulated during 2 months.
>>
>> But these patches need to be properly tested before going into LTS, right?
>> So it means extra effort for the validation teams?
>
> Exact
> The stable release must be validated anyway.
> The proposal is to validate the .1 release before starting RC1 validation,
> instead of doing it after the .0 release.
I have same concern with Konstantin.
Why merging unverified patches to the stable tree? It is not uncommon that we
fix fixes during rc phase.
I am for waiting proper release to backport fixes to the stable release.
For specific cases, like backporting a specific hot fixes to the stable, I
understand having stable release before actual release, but for that case the
scope and what to focus/test is limited and can be managed.
Is there a request received to get stable trees earlier? What is the motivation
of the change?
next prev parent reply other threads:[~2018-03-09 15:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 13:36 [dpdk-web] " Thomas Monjalon
2018-03-09 13:44 ` Luca Boccassi
2018-03-09 13:49 ` Thomas Monjalon
2018-03-09 14:03 ` [dpdk-web] [dpdk-techboard] " Ananyev, Konstantin
2018-03-09 14:19 ` Thomas Monjalon
2018-03-09 15:24 ` Ferruh Yigit [this message]
2018-03-09 15:45 ` Thomas Monjalon
2018-03-09 17:30 ` Luca Boccassi
2018-03-09 14:30 ` [dpdk-web] " Kevin Traynor
2018-03-09 14:51 ` Thomas Monjalon
2018-03-09 15:43 ` Kevin Traynor
2018-03-22 11:03 ` Luca Boccassi
2018-03-22 11:22 ` Luca Boccassi
2018-03-22 11:25 ` Thomas Monjalon
[not found] ` <1522937784.16877.28.camel@debian.org>
2018-04-05 14:19 ` Christian Ehrhardt
2018-04-05 14:23 ` Thomas Monjalon
2018-04-10 23:28 ` [dpdk-web] [PATCH v2] " 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 ` Ferruh Yigit
2018-04-18 9:14 ` Thomas Monjalon
2018-04-18 12:28 ` Ferruh Yigit
2018-04-18 13:28 ` Thomas Monjalon
2018-04-19 9:38 ` Kevin Traynor
2018-04-20 15:52 ` [dpdk-web] [dpdk-dev] " 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
2018-05-17 16:32 ` [dpdk-web] [PATCH v3] " Thomas Monjalon
2018-05-17 16:41 ` Ferruh Yigit
2018-05-17 16:59 ` 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=d0930c39-b522-9cf9-7191-c08d67ca5117@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bluca@debian.org \
--cc=konstantin.ananyev@intel.com \
--cc=ktraynor@redhat.com \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
--cc=yliu@fridaylinux.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).