On Wed, 2019-03-27 at 17:22 +0000, 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 facilitate user > planning, a release should be designated as a stable release > no later than 1 month after it's initial master release. > > Signed-off-by: Kevin Traynor < > ktray...@redhat.com > > > --- > > v2: add 1 month deadline to designate as stable release. > I didn't add v1 acks, as this is something new. > > doc/guides/contributing/stable.rst | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/doc/guides/contributing/stable.rst > b/doc/guides/contributing/stable.rst > index 4214103b3..b63cd4228 100644 > --- a/doc/guides/contributing/stable.rst > +++ b/doc/guides/contributing/stable.rst > @@ -27,5 +27,7 @@ Stable Releases > > Any major release of DPDK can be designated as a Stable Release if a > -maintainer volunteers to maintain it. > +maintainer volunteers to maintain it and there is a commitment from > major > +contributors to validate it before releases. If a release is to be > designated > +as a Stable Release, it should be done by 1 month after the master > release. > > A Stable Release is used to backport fixes from an ``N`` release > back to an
Acked-by: Luca Boccassi <bl...@debian.org> -- Kind regards, Luca Boccassi
