Thread (34 messages) flat view 34 messages, 9 authors, 2021-09-14

Re: [dpdk-dev] [PATCH v3 1/1] doc: add release milestones definition

From: Mcnamara, John <hidden>
Date: 2021-01-27 18:34:14

-----Original Message-----
From: dev <redacted> On Behalf Of Thomas Monjalon
Sent: Wednesday, January 13, 2021 9:12 AM
To: dev@dpdk.org
Cc: david.marchand@redhat.com; Yigit, Ferruh <redacted>; Asaf
Penso [off-list ref]
Subject: [dpdk-dev] [PATCH v3 1/1] doc: add release milestones definition

From: Asaf Penso <redacted>

Adding more information about the release milestones.
This includes the scope of change, expectations, etc.

First off, thanks for putting this together, it is a good initiative to document the processes we follow.

Some minor corrections/suggestions below.

+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 libs, drivers, apps, and examples.
+* Timeframe: to be published until the first day of the release cycle.
s/until/before

+rc2
+~~~
+
+* Content: 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.
+* At least 2 weeks before -rc2 the above should be sent to the ML for
review.
Maybe slightly better as:

 * The above should be sent to the mailing list at least 2 weeks before -rc2.
+rc3
+~~~
+
+* Content: test apps.
+* 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.
+* Big bug fixes.
Maybe instead of "Big bug fixes" we could use "Critical and minor bug fixes only"

+rc4
+~~~
+
+* Documentation updates.
+* Critical bug fixes.

Acked-by: John McNamara <redacted>



Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help