From: Ajit Khaparde <ajit.khaparde@broadcom.com> To: Thomas Monjalon <thomas@monjalon.net> Cc: dpdk-dev <dev@dpdk.org>, Asaf Penso <asafp@nvidia.com>, John McNamara <john.mcnamara@intel.com> Subject: Re: [dpdk-dev] [PATCH v4 1/1] doc: add release milestones definition Date: Mon, 1 Feb 2021 14:31:18 -0800 Message-ID: <CACZ4nhttoonGBX+JsQHOyb9XaMMkz1k3osrThsdhgdP2Z=RA3Q@mail.gmail.com> (raw) In-Reply-To: <20210201221333.2062052-1-thomas@monjalon.net> [-- Attachment #1: Type: text/plain, Size: 3864 bytes --] On Mon, Feb 1, 2021 at 2:13 PM Thomas Monjalon <thomas@monjalon.net> wrote: > > From: Asaf Penso <asafp@nvidia.com> > > Adding more information about the release milestones. > This includes the scope of change, expectations, etc. > > Signed-off-by: Asaf Penso <asafp@nvidia.com> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net> > Acked-by: John McNamara <john.mcnamara@intel.com> 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 >
next prev parent reply other threads:[~2021-02-01 22:31 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-10 18:44 [dpdk-dev] [PATCH] " Asaf Penso 2021-01-12 13:30 ` [dpdk-dev] [PATCH v2] " Michael Baum 2021-01-13 9:12 ` [dpdk-dev] [PATCH v3 1/1] " Thomas Monjalon 2021-01-27 18:33 ` Mcnamara, John 2021-02-01 22:13 ` [dpdk-dev] [PATCH v4 " Thomas Monjalon 2021-02-01 22:31 ` Ajit Khaparde [this message] 2021-02-01 22:38 ` Thomas Monjalon 2021-02-03 7:58 ` [dpdk-dev] [PATCH v5 " Thomas Monjalon 2021-02-03 10:14 ` David Marchand 2021-02-03 10:27 ` Thomas Monjalon 2021-03-28 19:00 ` [dpdk-dev] [PATCH v6] " Thomas Monjalon 2021-03-29 2:02 ` Ajit Khaparde 2021-05-18 11:57 ` Ferruh Yigit 2021-05-18 12:25 ` Thomas Monjalon 2021-05-18 13:13 ` Ferruh Yigit 2021-05-18 17:20 ` Ajit Khaparde 2021-05-18 16:43 ` [dpdk-dev] [PATCH v7] " Thomas Monjalon 2021-05-19 8:56 ` Bruce Richardson 2021-05-19 11:58 ` Ferruh Yigit 2021-05-19 12:16 ` Thomas Monjalon 2021-08-26 10:11 ` [dpdk-dev] [PATCH v8] " Thomas Monjalon 2021-09-02 16:33 ` Ferruh Yigit 2021-09-03 11:50 ` Thomas Monjalon 2021-09-03 15:35 ` Ferruh Yigit 2021-09-14 7:53 ` Thomas Monjalon 2021-09-14 16:11 ` Ajit Khaparde 2021-09-14 16:46 ` Thomas Monjalon 2021-09-03 12:26 ` Andrew Rybchenko 2021-09-03 12:55 ` Thomas Monjalon 2021-09-14 7:56 ` [dpdk-dev] [PATCH v9] " Thomas Monjalon 2021-09-14 16:34 ` Ferruh Yigit 2021-09-14 16:50 ` Thomas Monjalon 2021-09-14 16:51 ` Ajit Khaparde 2021-09-14 17:20 ` Thomas Monjalon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CACZ4nhttoonGBX+JsQHOyb9XaMMkz1k3osrThsdhgdP2Z=RA3Q@mail.gmail.com' \ --to=ajit.khaparde@broadcom.com \ --cc=asafp@nvidia.com \ --cc=dev@dpdk.org \ --cc=john.mcnamara@intel.com \ --cc=thomas@monjalon.net \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
DPDK patches and discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \ dev@dpdk.org public-inbox-index dev Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.dev AGPL code for this site: git clone https://public-inbox.org/public-inbox.git