Re: [dpdk-dev] [PATCH v2] doc: note validation and timeline required for stables

2019-04-05 Thread Thomas Monjalon
27/03/2019 18:25, Luca Boccassi: > On Wed, 2019-03-27 at 17:22 +, Kevin Traynor wrote: > > If a stable branch for a specific DPDK release is to proceed, > > along with needing a maintainer, there should also be commitment > > from major contributors for validation of the releases. > > > > Also

Re: [dpdk-dev] [PATCH v2] doc: note validation and timeline required for stables

2019-03-27 Thread Luca Boccassi
On Wed, 2019-03-27 at 17:22 +, Kevin Traynor wrote: > If a stable branch for a specific DPDK release is to proceed, > along with needing a maintainer, there should also be commitment > from major contributors for validation of the releases. > > Also, as decided in the March 27th techboard, to

[dpdk-dev] [PATCH v2] doc: note validation and timeline required for stables

2019-03-27 Thread Kevin Traynor
If a stable branch for a specific DPDK release is to proceed, along with needing a maintainer, there should also be commitment from major contributors for validation of the releases. Also, as decided in the March 27th techboard, to facilitate user planning, a release should be designated as a stab