From mboxrd@z Thu Jan  1 00:00:00 1970
From: Luca Boccassi <bluca@debian.org>
Subject: Re: [PATCH v2] doc: note validation and timeline
 required for stables
Date: Wed, 27 Mar 2019 17:25:47 +0000
Message-ID: <65000618657f3eef2b1ba5f802ea59bc0ff81d5e.camel@debian.org>
References: <20190322114400.3745-1-ktraynor@redhat.com>
 <20190327172206.16187-1-ktraynor@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: stable@dpdk.org
To: Kevin Traynor <ktraynor@redhat.com>, john.mcnamara@intel.com,
 marko.kovacevic@intel.com, dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
In-Reply-To: <20190327172206.16187-1-ktraynor@redhat.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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.
>=20
> 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.
>=20
> Signed-off-by: Kevin Traynor <
> ktraynor@redhat.com
> >
> ---
>=20
> v2: add 1 month deadline to designate as stable release.
> I didn't add v1 acks, as this is something new.
>=20
>  doc/guides/contributing/stable.rst | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>=20
> 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
> =20
>  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.
> =20
>  A Stable Release is used to backport fixes from an ``N`` release
> back to an

Acked-by: Luca Boccassi <bluca@debian.org>

--=20
Kind regards,
Luca Boccassi