[dpdk-web] [dpdk-techboard] [PATCH] update stable releases roadmap
ferruh.yigit at intel.com
Fri Mar 9 16:24:01 CET 2018
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 at monjalon.net>
>>>>> This is at the same time, a call for volunteer,
>>>>> and a proposed change to shorten the wait for the first stable
>>>>> from at least 3 months to 2 months.
>>>>> Let's add this discussion to the agenda of the next techboard
>>>> 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?
> 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?
More information about the web