doc: note validation and timeline required for stables
authorKevin Traynor <ktraynor@redhat.com>
Wed, 27 Mar 2019 17:22:06 +0000 (17:22 +0000)
committerThomas Monjalon <thomas@monjalon.net>
Fri, 5 Apr 2019 13:39:15 +0000 (15:39 +0200)
commitcf6b07d20660f79261f60049e0d4a64afbd64f27
tree1d7b485e37055ed3cad2546fe99f80270e820f1e
parentbb411b952d6c70dc93de22aa3d092e385239de6c
doc: note validation and timeline required for stables

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 <ktraynor@redhat.com>
Acked-by: Luca Boccassi <bluca@debian.org>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
doc/guides/contributing/stable.rst