* [dpdk-dev] [PATCH] doc: note validation commitment required for stables
2019-03-22 11:44 [dpdk-dev] [PATCH] doc: note validation commitment required for stables Kevin Traynor
@ 2019-03-22 11:44 ` Kevin Traynor
2019-03-22 13:30 ` Luca Boccassi
` (2 subsequent siblings)
3 siblings, 0 replies; 12+ messages in thread
From: Kevin Traynor @ 2019-03-22 11:44 UTC (permalink / raw)
To: dev, john.mcnamara, marko.kovacevic
Cc: stable, bluca, yskoh, ferruh.yigit, thomas, stephen, 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.
Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
---
doc/guides/contributing/stable.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/guides/contributing/stable.rst b/doc/guides/contributing/stable.rst
index 4214103b3..0130991e2 100644
--- a/doc/guides/contributing/stable.rst
+++ b/doc/guides/contributing/stable.rst
@@ -27,5 +27,6 @@ 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.
A Stable Release is used to backport fixes from an ``N`` release back to an
--
2.20.1
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [dpdk-dev] [PATCH] doc: note validation commitment required for stables
2019-03-22 11:44 [dpdk-dev] [PATCH] doc: note validation commitment required for stables Kevin Traynor
2019-03-22 11:44 ` Kevin Traynor
@ 2019-03-22 13:30 ` Luca Boccassi
2019-03-22 13:30 ` Luca Boccassi
2019-03-25 10:14 ` Kovacevic, Marko
2019-03-27 17:22 ` [dpdk-dev] [PATCH v2] doc: note validation and timeline " Kevin Traynor
3 siblings, 1 reply; 12+ messages in thread
From: Luca Boccassi @ 2019-03-22 13:30 UTC (permalink / raw)
To: Kevin Traynor, dev, john.mcnamara, marko.kovacevic
Cc: stable, yskoh, ferruh.yigit, thomas, stephen
On Fri, 2019-03-22 at 11:44 +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.
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> ---
> doc/guides/contributing/stable.rst | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/doc/guides/contributing/stable.rst
> b/doc/guides/contributing/stable.rst
> index 4214103b3..0130991e2 100644
> --- a/doc/guides/contributing/stable.rst
> +++ b/doc/guides/contributing/stable.rst
> @@ -27,5 +27,6 @@ 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.
>
> A Stable Release is used to backport fixes from an ``N`` release
> back to an
Acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [dpdk-dev] [PATCH] doc: note validation commitment required for stables
2019-03-22 13:30 ` Luca Boccassi
@ 2019-03-22 13:30 ` Luca Boccassi
0 siblings, 0 replies; 12+ messages in thread
From: Luca Boccassi @ 2019-03-22 13:30 UTC (permalink / raw)
To: Kevin Traynor, dev, john.mcnamara, marko.kovacevic
Cc: stable, yskoh, ferruh.yigit, thomas, stephen
On Fri, 2019-03-22 at 11:44 +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.
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> ---
> doc/guides/contributing/stable.rst | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/doc/guides/contributing/stable.rst
> b/doc/guides/contributing/stable.rst
> index 4214103b3..0130991e2 100644
> --- a/doc/guides/contributing/stable.rst
> +++ b/doc/guides/contributing/stable.rst
> @@ -27,5 +27,6 @@ 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.
>
> A Stable Release is used to backport fixes from an ``N`` release
> back to an
Acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [dpdk-dev] [PATCH] doc: note validation commitment required for stables
2019-03-22 11:44 [dpdk-dev] [PATCH] doc: note validation commitment required for stables Kevin Traynor
2019-03-22 11:44 ` Kevin Traynor
2019-03-22 13:30 ` Luca Boccassi
@ 2019-03-25 10:14 ` Kovacevic, Marko
2019-03-25 10:14 ` Kovacevic, Marko
2019-03-27 17:22 ` [dpdk-dev] [PATCH v2] doc: note validation and timeline " Kevin Traynor
3 siblings, 1 reply; 12+ messages in thread
From: Kovacevic, Marko @ 2019-03-25 10:14 UTC (permalink / raw)
To: Kevin Traynor, dev, Mcnamara, John
Cc: stable, bluca, yskoh, Yigit, Ferruh, thomas, stephen
> Subject: [PATCH] doc: note validation commitment 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.
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> ---
> doc/guides/contributing/stable.rst | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/doc/guides/contributing/stable.rst
> b/doc/guides/contributing/stable.rst
> index 4214103b3..0130991e2 100644
> --- a/doc/guides/contributing/stable.rst
> +++ b/doc/guides/contributing/stable.rst
> @@ -27,5 +27,6 @@ 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.
>
> A Stable Release is used to backport fixes from an ``N`` release back to an
> --
Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [dpdk-dev] [PATCH] doc: note validation commitment required for stables
2019-03-25 10:14 ` Kovacevic, Marko
@ 2019-03-25 10:14 ` Kovacevic, Marko
0 siblings, 0 replies; 12+ messages in thread
From: Kovacevic, Marko @ 2019-03-25 10:14 UTC (permalink / raw)
To: Kevin Traynor, dev, Mcnamara, John
Cc: stable, bluca, yskoh, Yigit, Ferruh, thomas, stephen
> Subject: [PATCH] doc: note validation commitment 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.
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> ---
> doc/guides/contributing/stable.rst | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/doc/guides/contributing/stable.rst
> b/doc/guides/contributing/stable.rst
> index 4214103b3..0130991e2 100644
> --- a/doc/guides/contributing/stable.rst
> +++ b/doc/guides/contributing/stable.rst
> @@ -27,5 +27,6 @@ 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.
>
> A Stable Release is used to backport fixes from an ``N`` release back to an
> --
Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
^ permalink raw reply [flat|nested] 12+ messages in thread
* [dpdk-dev] [PATCH v2] doc: note validation and timeline required for stables
2019-03-22 11:44 [dpdk-dev] [PATCH] doc: note validation commitment required for stables Kevin Traynor
` (2 preceding siblings ...)
2019-03-25 10:14 ` Kovacevic, Marko
@ 2019-03-27 17:22 ` Kevin Traynor
2019-03-27 17:22 ` Kevin Traynor
2019-03-27 17:25 ` Luca Boccassi
3 siblings, 2 replies; 12+ messages in thread
From: Kevin Traynor @ 2019-03-27 17:22 UTC (permalink / raw)
To: john.mcnamara, marko.kovacevic, dev; +Cc: bluca, stable, 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 stable release
no later than 1 month after it's initial master release.
Signed-off-by: Kevin Traynor <ktraynor@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
--
2.20.1
^ permalink raw reply [flat|nested] 12+ messages in thread* [dpdk-dev] [PATCH v2] doc: note validation and timeline required for stables
2019-03-27 17:22 ` [dpdk-dev] [PATCH v2] doc: note validation and timeline " Kevin Traynor
@ 2019-03-27 17:22 ` Kevin Traynor
2019-03-27 17:25 ` Luca Boccassi
1 sibling, 0 replies; 12+ messages in thread
From: Kevin Traynor @ 2019-03-27 17:22 UTC (permalink / raw)
To: john.mcnamara, marko.kovacevic, dev; +Cc: bluca, stable, 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 stable release
no later than 1 month after it's initial master release.
Signed-off-by: Kevin Traynor <ktraynor@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
--
2.20.1
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [dpdk-dev] [PATCH v2] doc: note validation and timeline required for stables
2019-03-27 17:22 ` [dpdk-dev] [PATCH v2] doc: note validation and timeline " Kevin Traynor
2019-03-27 17:22 ` Kevin Traynor
@ 2019-03-27 17:25 ` Luca Boccassi
2019-03-27 17:25 ` Luca Boccassi
2019-04-05 13:36 ` Thomas Monjalon
1 sibling, 2 replies; 12+ messages in thread
From: Luca Boccassi @ 2019-03-27 17:25 UTC (permalink / raw)
To: Kevin Traynor, john.mcnamara, marko.kovacevic, dev; +Cc: stable
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 <
> ktraynor@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 <bluca@debian.org>
--
Kind regards,
Luca Boccassi
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [dpdk-dev] [PATCH v2] doc: note validation and timeline required for stables
2019-03-27 17:25 ` Luca Boccassi
@ 2019-03-27 17:25 ` Luca Boccassi
2019-04-05 13:36 ` Thomas Monjalon
1 sibling, 0 replies; 12+ messages in thread
From: Luca Boccassi @ 2019-03-27 17:25 UTC (permalink / raw)
To: Kevin Traynor, john.mcnamara, marko.kovacevic, dev; +Cc: stable
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 <
> ktraynor@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 <bluca@debian.org>
--
Kind regards,
Luca Boccassi
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [dpdk-dev] [PATCH v2] doc: note validation and timeline required for stables
2019-03-27 17:25 ` Luca Boccassi
2019-03-27 17:25 ` Luca Boccassi
@ 2019-04-05 13:36 ` Thomas Monjalon
2019-04-05 13:36 ` Thomas Monjalon
1 sibling, 1 reply; 12+ messages in thread
From: Thomas Monjalon @ 2019-04-05 13:36 UTC (permalink / raw)
To: Kevin Traynor; +Cc: dev, Luca Boccassi, john.mcnamara, marko.kovacevic, stable
27/03/2019 18:25, Luca Boccassi:
> 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 <ktraynor@redhat.com>
> > ---
> >
> > v2: add 1 month deadline to designate as stable release.
> > I didn't add v1 acks, as this is something new.
> >
> > --- 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 <bluca@debian.org>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
Applied, thanks
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [dpdk-dev] [PATCH v2] doc: note validation and timeline required for stables
2019-04-05 13:36 ` Thomas Monjalon
@ 2019-04-05 13:36 ` Thomas Monjalon
0 siblings, 0 replies; 12+ messages in thread
From: Thomas Monjalon @ 2019-04-05 13:36 UTC (permalink / raw)
To: Kevin Traynor; +Cc: dev, Luca Boccassi, john.mcnamara, marko.kovacevic, stable
27/03/2019 18:25, Luca Boccassi:
> 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 <ktraynor@redhat.com>
> > ---
> >
> > v2: add 1 month deadline to designate as stable release.
> > I didn't add v1 acks, as this is something new.
> >
> > --- 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 <bluca@debian.org>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
Applied, thanks
^ permalink raw reply [flat|nested] 12+ messages in thread