From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f65.google.com (mail-wm0-f65.google.com [74.125.82.65]) by dpdk.org (Postfix) with ESMTP id 745C32BF1; Thu, 22 Mar 2018 12:22:10 +0100 (CET) Received: by mail-wm0-f65.google.com with SMTP id l9so15267845wmh.2; Thu, 22 Mar 2018 04:22:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-transfer-encoding:mime-version; bh=8JeMfbZ2nTgu0HR4kpHcKAMdyX4AGs6hI7T9cdZTo+4=; b=bw2J6sfiuCrt5MQuwrWBRVKQ7UO0DP0BzilFeGFfq6pGmpGa5rk16DLGMTarceCxHK 3A/FJCXBTQ9S3v4qZTl1tNd1XOzlk9diTEyCsPDVofV/zQGqgSA/Zt+GXqGtuesHIyuJ Vw3hiueLEfiKDSapBkXCaEdqy6zNTdsI/mTZkgxBdNSkwKgCnZnFyhzKOzqjV5AsgtcC 8u3ZQm7+eCZZGI1OGsjHqTeNrI6ObGghQzpxPMLvk/CJi1mgnbjHDsVkFw4io0dyfSzx CN3B0LH0gLKqwZiOwbszTYHpTXAL2lmrcmXiE/thrTERjy+tq+aI4jQAXVu1eZfM7eTY HdgQ== X-Gm-Message-State: AElRT7EfP0QzrBn7NrUZ2PP9bgv4GUm/XU/e6kYuIRQhmtoduUX53cmG Vz3g2JVdwQu9C86S7ngZ/rg= X-Google-Smtp-Source: AG47ELu8CXDEiIFzErWb25Q1fB0E2FOw4EW2Ic96Ye798bxcYBnKz8TX0pe7NN79D0i4l1T3+ugnBg== X-Received: by 10.28.85.194 with SMTP id j185mr4700218wmb.118.1521717730050; Thu, 22 Mar 2018 04:22:10 -0700 (PDT) Received: from localhost ([213.251.34.146]) by smtp.gmail.com with ESMTPSA id v191sm3014592wmf.34.2018.03.22.04.22.09 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 22 Mar 2018 04:22:09 -0700 (PDT) Message-ID: <1521717727.14111.58.camel@debian.org> From: Luca Boccassi To: Thomas Monjalon , web@dpdk.org Cc: yliu@fridaylinux.org, ktraynor@redhat.com, techboard@dpdk.org, john.mcnamara@intel.com Date: Thu, 22 Mar 2018 11:22:07 +0000 In-Reply-To: <1521716595.14111.56.camel@debian.org> References: <20180309133612.19927-1-thomas@monjalon.net> <1521716595.14111.56.camel@debian.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Subject: Re: [dpdk-web] [PATCH] update stable releases roadmap X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 11:22:10 -0000 On Thu, 2018-03-22 at 11:03 +0000, Luca Boccassi wrote: > On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote: > > Signed-off-by: Thomas Monjalon > >=20 > > --- > > 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. > >=20 > > Let's add this discussion to the agenda of the next techboard > > meeting. > > --- > > =C2=A0dev/roadmap.html | 35 +++++++++++++++++++++++++++++++---- > > =C2=A01 file changed, 31 insertions(+), 4 deletions(-) > >=20 > > diff --git a/dev/roadmap.html b/dev/roadmap.html > > index e6cf640..e40f410 100644 > > --- a/dev/roadmap.html > > +++ b/dev/roadmap.html > > @@ -104,6 +104,8 @@ > > =C2=A0
  • Release: November 2, 2018 > > =C2=A0 > > =C2=A0

    Stable releases

    > > +

    There is a documentation page describing the > > + guidelines > > of > > the stable releases. > > =C2=A0

    Stable point releases follow mainline releases. > > =C2=A0

    After each -rc tag and after the final version, > > relevant > > bug fixes get > > =C2=A0 backported by the stable maintainers into the respective > > branches in "bursts". > > @@ -111,8 +113,9 @@ > > =C2=A0 to stable@dpdk.org only (avoiding dev@dpdk.org). > > =C2=A0

    After all the relevant bugfixes have been backported, > > =C2=A0 regression tests are ran, and if clear, the stable release > > is announced. > > -

    Typically a new stable release version follows a > > mainline > > release > > - by 1-2 weeks, depending on the test results. > > +

    The first stable release (.1) of a branch should follow > > + its mainline release (.0) by two months, > > + before starting tests of the next mainline release > > candidates. > > =C2=A0

    > > =C2=A0
    > > =C2=A0 > > @@ -125,15 +128,39 @@ > > =C2=A0 > > =C2=A0 > > =C2=A0 > > - > > + > > =C2=A0 > > =C2=A0 > > =C2=A0 > > =C2=A0 > > =C2=A0 > > - > > + > > =C2=A0 > > =C2=A0 > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > =C2=A0
    16.11.6May 19, 2018November 2018November 2018 (LTS)Luca Boccassi
    17.11.2May 19, 2018November 2019November 2019 (LTS)Yuanhan Liu
    18.02.1April 6, 2018June 2018looking for volunteer
    18.05.1June 29, 2018October 2018looking for volunteer
    18.08.1October 5, 2018January 2019looking for volunteer
    18.11.1January 11, 2019November 2020 (LTS)looking for volunteer
    > > =C2=A0
    > > =C2=A0 >=20 > Hi, >=20 > I'm happy to help with 18.02.1. >=20 > Given it will be based on 18.05-rc2, which is due out on > approximately > April 20th, I think we can be ambitious and target April 27th as the > tentative release date. >=20 > Note that ATT won't be able to help with regression tests this time > around. John, may we count on help from Intel to run the usual batch > of > regression tests between the 20th and the 27th? Slight misunderstanding, sorry - we'll want to base 18.02.1 on 18.05- rc1 (not rc2), which means the dates get pulled forward by 10 days - I'll make the branch available for review and eventually ask for help from backporters if needed on April the 10th, and ambitiously targeting release for April the 17th. So we'd need regression tests done before the 17th of April. --=20 Kind regards, Luca Boccassi