From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7A310A0C52 for ; Tue, 23 Nov 2021 16:06:16 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id F3F7740040; Tue, 23 Nov 2021 16:06:15 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 5C1DF41143 for ; Fri, 19 Nov 2021 14:48:51 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1637329730; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=r6HWSTGfS7tgdXAJ6wwres0p3jAc7EjOX149cWa7U8c=; b=NQUWewsAX8gB/ovNv9kBCZB3tQe7akHRQ5cgbO/Ar/dF9H2h9PtpzBVxiIjZwFxVcHmenR 4MhT7matshR3yUXr6G8r0dXQVUJJo8itwZnnP/OYghIZrtjknS6Ehs4MXmrob7OY06KdCq 7VielJZaKDGRUgG3yIjL6DTD2ACWCqU= Received: from mail-lf1-f69.google.com (mail-lf1-f69.google.com [209.85.167.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-278-FwMNWL9yN_qE1u8zyaFxBw-1; Fri, 19 Nov 2021 08:48:47 -0500 X-MC-Unique: FwMNWL9yN_qE1u8zyaFxBw-1 Received: by mail-lf1-f69.google.com with SMTP id s18-20020ac25c52000000b004016bab6a12so6663172lfp.21 for ; Fri, 19 Nov 2021 05:48:47 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=r6HWSTGfS7tgdXAJ6wwres0p3jAc7EjOX149cWa7U8c=; b=aIfWy0Xr6XKj16WpoEPw7+bzldWcb9c+rESfsyoKCVqeL5wJnP3THTTKzc3yzlY5hN GozcqOOiUFbnNuQ5yFY1+1hMHJboAiJAZpsJdqewRS+qJc7HRN0fFcCoYMw58tVE93qT vzgKOk8nRyINLQR2eJ3UMVZ/EcP0p2dKeL7YaNVWI02XwelUPmp+5TpnZX7j7vhEviG3 7mGr38PUtB59+91BIdYQjWdCfR4g8cAczeR6m3YbO6wPHc5Y4X0aMVf2txCEFiDhwXE3 aBlyjB4QQht4issQh1Z9iVbRgVAyXzhrfidaSlx3w0XqZLdh1mPCS0ruQ1NZwkvapo0w NJyg== X-Gm-Message-State: AOAM530LwqM9wfhaMO1MenwDRZqB0asMK2OI+ZT+vfsUk1c4J5shyvy/ YIPg3a3ZMp3jqZbQLkIoumffSqhA/w/2FEDMDl2D4Nk0+J6d8QWebAvfsaIBDj/C+UDQ4Rg0rfT Fq0dN5sjBbMN0CnEXTbEEUQ== X-Received: by 2002:ac2:5e8f:: with SMTP id b15mr33281584lfq.252.1637329725926; Fri, 19 Nov 2021 05:48:45 -0800 (PST) X-Google-Smtp-Source: ABdhPJyTXrLU/vkSfHGPA8w5fastjm/0+lO2WvfsWF/LBISLOOL08LO5OaQV/MzzG8cLau0NLGxOxlmuKRv9LKTnfZ0= X-Received: by 2002:ac2:5e8f:: with SMTP id b15mr33281531lfq.252.1637329725687; Fri, 19 Nov 2021 05:48:45 -0800 (PST) MIME-Version: 1.0 References: <5786413.XMpytKYiJR@thomas> <4b5ad9da-585d-37ef-198c-6c4e6d6ad9aa@redhat.com> In-Reply-To: <4b5ad9da-585d-37ef-198c-6c4e6d6ad9aa@redhat.com> From: Flavio Leitner Date: Fri, 19 Nov 2021 10:48:34 -0300 Message-ID: Subject: Re: release schedule change proposal To: Kevin Traynor Cc: Thomas Monjalon , dev@dpdk.org, users@dpdk.org, David Marchand , ferruh.yigit@intel.com, andrew.rybchenko@oktetlabs.ru, qi.z.zhang@intel.com, jerinj@marvell.com, rasland@nvidia.com, Maxime Coquelin , gakhil@marvell.com, Luca Boccassi , "Richardson, Bruce" , mdr@ashroe.eu, konstantin.ananyev@intel.com, olivier.matz@6wind.com, honnappa.nagarahalli@arm.com, hemant.agrawal@nxp.com, Aaron Conole , ajit.khaparde@broadcom.com, Ilya Maximets , Ian Stokes , ovs-discuss , Timothy Redaelli Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=fleitner@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: multipart/alternative; boundary="000000000000ae217605d1248863" X-Mailman-Approved-At: Tue, 23 Nov 2021 16:06:15 +0100 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --000000000000ae217605d1248863 Content-Type: text/plain; charset="UTF-8" Thanks Kevin for bringing this up. See below. On Mon, Nov 15, 2021 at 1:06 PM Kevin Traynor wrote: > On 15/11/2021 14:58, Thomas Monjalon wrote: > > For the last 5 years, DPDK was doing 4 releases per year, > > in February, May, August and November (the LTS one): > > .02 .05 .08 .11 (LTS) > > > > This schedule has multiple issues: > > - clash with China's Spring Festival > > - too many rushes, impacting maintainers & testers > > - not much buffer, impacting proposal period > > > > I propose to switch to a new schedule with 3 releases per year: > > .03 .07 .11 (LTS) > > > > New LTS branch would start at the same time of the year as before. > > There would be one less intermediate release during spring/summer: > > .05 and .08 intermediate releases would become a single .07. > > I think it has almost no impact for the users. > > This change could be done starting next year. > > > > In details, this is how we could extend some milestones: > > > > ideal schedule so far (in 13 weeks): > > proposal deadline: 4 > > rc1 - API freeze: 5 > > rc2 - PMD features freeze: 2 > > rc3 - app features freeze: 1 > > rc4 - last chance to fix: 1 > > release: 0 > > > > proposed schedule (in 17 weeks): > > proposal deadline: 4 > > rc1 - API freeze: 7 > > rc2 - PMD features freeze: 3 > > rc3 - app features freeze: 1 > > rc4 - more fixes: 1 > > rc5 - last chance buffer: 1 > > release: 0 > > > > Opinions? > > > > > > Someone else might comment if they spot something, but to me looks ok > for RH distro and OVS project. > That is my impression as well. > > RH distro is also using DPDK .11 who's release date is not changing. > (+cc Timothy/Flavio) > My concern is if patches would get delayed to be merged because of this change, but I don't think that will be the case. > For OVS project, it only integrates DPDK .11 release too and aims to do > that by EOY to make the next OVS release. DPDK stable releases are > integrated into older OVS branches when available. I don't think older > OVS branch releases have a strict release schedule and having the latest > stable DPDK release is not a blocker anyway. (+cc Ilya/Ian/ovs-discuss) > I agree. fbl --000000000000ae217605d1248863 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks Kevin for bringing this up.
See belo= w.

On Mon, Nov 15, 2021 at 1:06 PM Kevin Traynor <ktraynor@redhat.com> wrote:
On 15/11/2021 14:58, Thomas Monjalon wro= te:
> For the last 5 years, DPDK was doing 4 releases per year,
> in February, May, August and November (the LTS one):
>=C2=A0 =C2=A0 =C2=A0 =C2=A0.02=C2=A0 =C2=A0.05=C2=A0 =C2=A0.08=C2=A0 = =C2=A0.11 (LTS)
>
> This schedule has multiple issues:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0- clash with China's Spring Festival
>=C2=A0 =C2=A0 =C2=A0 =C2=A0- too many rushes, impacting maintainers &am= p; testers
>=C2=A0 =C2=A0 =C2=A0 =C2=A0- not much buffer, impacting proposal period=
>
> I propose to switch to a new schedule with 3 releases per year:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0.03=C2=A0 =C2=A0 =C2=A0 .07=C2=A0 =C2=A0 =C2= =A0 .11 (LTS)
>
> New LTS branch would start at the same time of the year as before.
> There would be one less intermediate release during spring/summer:
> .05 and .08 intermediate releases would become a single .07.
> I think it has almost no impact for the users.
> This change could be done starting next year.
>
> In details, this is how we could extend some milestones:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0ideal schedule so far (in 13 weeks):
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0proposal deadlin= e: 4
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0rc1 - API freeze= : 5
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0rc2 - PMD featur= es freeze: 2
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0rc3 - app featur= es freeze: 1
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0rc4 - last chanc= e to fix: 1
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0release: 0
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0proposed schedule (in 17 weeks):
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0proposal deadlin= e: 4
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0rc1 - API freeze= : 7
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0rc2 - PMD featur= es freeze: 3
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0rc3 - app featur= es freeze: 1
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0rc4 - more fixes= : 1
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0rc5 - last chanc= e buffer: 1
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0release: 0
>
> Opinions?
>
>

Someone else might comment if they spot something, but to me looks ok
for RH distro and OVS project.

That is = my impression as well.
=C2=A0

RH distro is also using DPDK .11 who's release date is not changing. (+cc Timothy/Flavio)

My concern is if p= atches would get delayed to be merged because of this
change, but= I don't think that will be the case.
=C2=A0
For OVS project, it only integrates DPDK .11 release too and aims to do that by EOY to make the next OVS release. DPDK stable releases are
integrated into older OVS branches when available. I don't think older =
OVS branch releases have a strict release schedule and having the latest stable DPDK release is not a blocker anyway. (+cc Ilya/Ian/ovs-discuss)
=

I agree.

fbl=C2= =A0
--000000000000ae217605d1248863--