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 26EFCA0A0B; Mon, 1 Feb 2021 23:31:37 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9E08A160655; Mon, 1 Feb 2021 23:31:36 +0100 (CET) Received: from mail-qv1-f42.google.com (mail-qv1-f42.google.com [209.85.219.42]) by mails.dpdk.org (Postfix) with ESMTP id D093B40693 for ; Mon, 1 Feb 2021 23:31:35 +0100 (CET) Received: by mail-qv1-f42.google.com with SMTP id 2so9031264qvd.0 for ; Mon, 01 Feb 2021 14:31:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=R5wI9y5PymdP9iVY95nB6ahMa37Sw1F1xVKx1jHpZbQ=; b=RpfY4w8ZiNRqqLYYIdthIaxO75SgyP/xsD57aJOB0n510J+A+y02jVVkS7cXWP59jy FBJXdxplmKil8GZtrKWKE6Yr2RyKanFUFev454A4St3H7FSA7Hk0QxB6cvm8CVwTjJwC C06DfyO/aa7oqpBLPvifaWTeTOAhlOJLRxiR0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=R5wI9y5PymdP9iVY95nB6ahMa37Sw1F1xVKx1jHpZbQ=; b=uG4zd6F/T+21iXloxjrc/OTM2PUXxTCzhQkA47PL3QZ0IQ6PJFI52YgXRfIB3sC7xy D/OzQ9vc4VkgM07MNwCNdUPDS2NFnZwcC2RrYqqEvA9NqEjgXxE45ackMJ/CdYop492x Lvkwv9PCp9Yzy+gtxeqGRrAytr5Xoht6XyzyXtjLAsAAoaZkSUGy3fR65zTjbgclhCWC qh6toH+zI7g8dE/DUaKaJ5u3HOSm/WALCEH5t4lqHwpNUkHRRQymCXmJlM/uJcxfyjYA 7i/+Jv5p9Rr7sZO5THn7Bmz9uqjlSF1mNtBh3+0dX0fGn9wddy1tcP5Yde+hOo3nNoSQ iRWg== X-Gm-Message-State: AOAM530n4JG9CTBjgZGUZm8aGQzcGW81UV08t3V/M2baGD8eHTcULGgO WwqcHGLnXQjwstWM8nRGusy/WdsrfO6DwC0tow2eBAeCz4E= X-Google-Smtp-Source: ABdhPJzjO4j+Ya8tO9PUz20vlePtzeCERPhLDLaEsR2BZEJ6DwAVJkRjCDZK53IbhjOZYx7vhqJhBoQnAdN7+/eA/zI= X-Received: by 2002:a0c:b929:: with SMTP id u41mr17602840qvf.30.1612218695041; Mon, 01 Feb 2021 14:31:35 -0800 (PST) MIME-Version: 1.0 References: <1610304247-11455-1-git-send-email-asafp@nvidia.com> <20210201221333.2062052-1-thomas@monjalon.net> In-Reply-To: <20210201221333.2062052-1-thomas@monjalon.net> From: Ajit Khaparde Date: Mon, 1 Feb 2021 14:31:18 -0800 Message-ID: To: Thomas Monjalon Cc: dpdk-dev , Asaf Penso , John McNamara Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="000000000000a4051005ba4deaa6" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [dpdk-dev] [PATCH v4 1/1] doc: add release milestones definition X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" --000000000000a4051005ba4deaa6 Content-Type: text/plain; charset="UTF-8" On Mon, Feb 1, 2021 at 2:13 PM Thomas Monjalon wrote: > > From: Asaf Penso > > Adding more information about the release milestones. > This includes the scope of change, expectations, etc. > > Signed-off-by: Asaf Penso > Signed-off-by: Thomas Monjalon > Acked-by: John McNamara Looks good to me. Can we add a mention somewhere that under some circumstances an rc5 may be required or the rc enumeration could change in some rare case, like when we had to spin a new rc during 20.11? > --- > v2: fix styling format and add content in the commit message > v3: change punctuation and avoid plural form when unneeded > v4: avoid abbreviations, "Priority" in -rc, and reword as John suggests > --- > doc/guides/contributing/patches.rst | 72 +++++++++++++++++++++++++++++ > 1 file changed, 72 insertions(+) > > diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst > index 6dbbd5f8d1..15739a43dc 100644 > --- a/doc/guides/contributing/patches.rst > +++ b/doc/guides/contributing/patches.rst > @@ -660,3 +660,75 @@ patch accepted. The general cycle for patch review and acceptance is: > than rework of the original. > * Trivial patches may be merged sooner than described above at the tree committer's > discretion. > + > + > +Milestones definition > +--------------------- > + > +Each DPDK release has milestones that help everyone to converge to the release date. > +The following is a list of these milestones > +together with concrete definitions and expectations. > + > +Roadmap > +~~~~~~~ > + > +* Content: new features in libraries, drivers, applications, and examples. > +* Timeframe: to be published before the first day of the release cycle. > + > +RFC > +~~~ > + > +* Content: public design review for the feature, explaining the need and the design. > +* Should include the API changes, in libraries and applications. > +* RFC is not mandatory but strongly advised to start early discussion. > +* Nice to have: driver implementation (full or draft), example code, and documentation. > + > +Proposal Deadline > +~~~~~~~~~~~~~~~~~ > + > +* Content: either an RFC as stated above or a v1 patch. > +* Nice to have: code complete for libraries. > + > +rc1 > +~~~ > + > +* Priority: new or updated API. > +* New API should be defined and implemented in libraries. > +* The API should include Doxygen documentation > + and be part of the relevant .rst files (library, release notes). > +* Code and related documentation must be updated atomically in the same patch. > +* API should be used in a test application (``/app``). > +* At least one PMD should implement the API. > + It can be a draft but must be sent as a separate series. > +* The above should be sent to the mailing list at least 2 weeks before -rc1. > +* Nice to have: example code (``/examples``) > + > +rc2 > +~~~ > + > +* Priority: drivers. > +* New features should be implemented in drivers. > +* A driver change should include documentation > + in the relevant .rst files (driver, release notes). > +* Code and related documentation must be updated atomically in the same patch. > +* The above should be sent to the mailing list at least 2 weeks before -rc2. > + > +rc3 > +~~~ > + > +* Priority: applications. > +* New functionality that does not depend on libs update > + can be integrated as part of -rc3. > +* The app should include documentation in the relevant .rst files > + (app, release notes if significant). > +* Code and related documentation must be updated atomically in the same patch. > +* Last opportunity for miscellaneous changes. > +* Libs and drivers cleanup. > +* Small driver reworks. > +* Critical and minor bug fixes. > + > +rc4 > +~~~ > + > +* Documentation updates. > +* Critical bug fixes. > -- > 2.30.0 > --000000000000a4051005ba4deaa6--