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 92869A034F; Mon, 29 Mar 2021 04:03:14 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0E35D4069D; Mon, 29 Mar 2021 04:03:14 +0200 (CEST) Received: from mail-qt1-f170.google.com (mail-qt1-f170.google.com [209.85.160.170]) by mails.dpdk.org (Postfix) with ESMTP id AA7A740042 for ; Mon, 29 Mar 2021 04:03:12 +0200 (CEST) Received: by mail-qt1-f170.google.com with SMTP id 1so7724105qtb.0 for ; Sun, 28 Mar 2021 19:03:12 -0700 (PDT) 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=u5ZcnO0r2TZQZ1VuVpC64ITR8048BMYtdFfPj8aLZWk=; b=Ma/JDnhhpyZOqmn8Zm+HM5vwgJOgezH4zXFtgnV3Hyezg66Pxh6H8OROgcwtA+YWB2 LApj1753RjVq3yOZfPChBCzyUFdSJOsXcMPd/yIZawuRFux82kLIgRcZrqRniaYsc6dL VFziqnWneqW0HN+S/8eqAt4lXEbfMaBrpccEk= 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=u5ZcnO0r2TZQZ1VuVpC64ITR8048BMYtdFfPj8aLZWk=; b=JRpuPS7ShSvFsnB9//cGtyoU3NsObrqembl8JKh5OTV2AqD4z1xMBatILG1eMGpz7v rD3fjH3AdHFafeLR+lRgIxFme41x//fsmiFa+7g0O+rAG1oX+rwnhVmIWPryV4xNL7yL Uge0x16/NyNOMFrEqWOBLDhL2cJTHbvJUHyFDFYeNGUuMeyyePbiqZCKyQVcCaYzVj6F UDEPfORlFdpfC5ftB6gOt5ht+/z40QrISskjPPyC6xpaFPkLUxvWuefeoQMUJotrDabT mWDu7QsAi+5WlcjQmwrHix34cvkmAr916N3/rsLjTpgebTUdxGHBZ6qWvef7pIeKjFvC Ptng== X-Gm-Message-State: AOAM530pCgvpENcyOmAZJh3y+Swc8QZoZ8OwRvj1WCSZhj/72uj2any5 faPb8EaesPMqN9xvvpevJMHOz9EulEz8v977R6GMIA== X-Google-Smtp-Source: ABdhPJzqw2A2d8OGyqSpVhTEgSgIPxiFFeZQHZGM6Ng2ZuMYjxR33bndmhajgaFI8Kx04sW4ZwlvhBR8/Zkjf77O6Jg= X-Received: by 2002:ac8:73c4:: with SMTP id v4mr21294237qtp.208.1616983391769; Sun, 28 Mar 2021 19:03:11 -0700 (PDT) MIME-Version: 1.0 References: <1610304247-11455-1-git-send-email-asafp@nvidia.com> <20210328190005.4185594-1-thomas@monjalon.net> In-Reply-To: <20210328190005.4185594-1-thomas@monjalon.net> From: Ajit Khaparde Date: Sun, 28 Mar 2021 19:02:55 -0700 Message-ID: To: Thomas Monjalon Cc: dpdk-dev , David Marchand , Asaf Penso , John McNamara Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="000000000000b351fa05bea348a0" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [dpdk-dev] [PATCH v6] 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" --000000000000b351fa05bea348a0 Content-Type: text/plain; charset="UTF-8" On Sun, Mar 28, 2021 at 12:00 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 Acked-by: Ajit Khaparde > --- > 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 > v5: note that release candidates may vary > v6: merge RFC and proposal deadline, add roadmap link and reduce duplication > --- > doc/guides/contributing/patches.rst | 69 +++++++++++++++++++++++++++++ > 1 file changed, 69 insertions(+) > > diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst > index 6dbbd5f8d1..1277443620 100644 > --- a/doc/guides/contributing/patches.rst > +++ b/doc/guides/contributing/patches.rst > @@ -177,6 +177,8 @@ Make your planned changes in the cloned ``dpdk`` repo. Here are some guidelines > * Add documentation, if relevant, in the form of Doxygen comments or a User Guide in RST format. > See the :ref:`Documentation Guidelines `. > > +* Code and related documentation must be updated atomically in the same patch. > + > Once the changes have been made you should commit them to your local repo. > > For small changes, that do not require specific explanations, it is better to keep things together in the > @@ -660,3 +662,70 @@ 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, > +for a typical release cycle (3 months ending after 4 release candidates). > +The number and expectations of release candidates might vary slightly. > +The schedule is updated in the `roadmap `_. > + > +Roadmap > +~~~~~~~ > + > +* Announce new features in libraries, drivers, applications, and examples. > +* To be published before the first day of the release cycle. > + > +Proposal Deadline > +~~~~~~~~~~~~~~~~~ > + > +* Must send an RFC or a complete v1 patch. > +* Early RFC gives time for design review before complete implementation. > +* Should include at least the API changes in libraries and applications. > +* Library code should be quite complete at the deadline. > +* Nice to have: driver implementation (full or draft), example code, and documentation. > + > +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-specific and release notes). > +* 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-specific and release notes). > +* 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 libraries update > + can be integrated as part of -rc3. > +* The application should include documentation in the relevant .rst files > + (application-specific and release notes if significant). > +* It may be the last opportunity for miscellaneous changes. > +* Libraries and drivers cleanup are allowed. > +* Small driver reworks. > +* Critical and minor bug fixes. > + > +rc4 > +~~~ > + > +* Documentation updates. > +* Critical bug fixes. > -- > 2.30.1 > --000000000000b351fa05bea348a0--