| Message ID | 20171031162855.5707-1-luca.boccassi@gmail.com (mailing list archive) |
|---|---|
| State | Accepted, archived |
| Headers | show |
| Context | Check | Description |
|---|---|---|
| ci/checkpatch | success | coding style OK |
| ci/Intel-compilation | success | Compilation OK |
> -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of > luca.boccassi@gmail.com > Sent: Tuesday, October 31, 2017 4:29 PM > To: dev@dpdk.org > Cc: thomas@monjalon.net; Luca Boccassi <bluca@debian.org> > Subject: [dpdk-dev] [PATCH] doc/guides: mention 17.11 LTS in > contributing/stable > > From: Luca Boccassi <bluca@debian.org> > > Signed-off-by: Luca Boccassi <bluca@debian.org> > --- > doc/guides/contributing/stable.rst | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/doc/guides/contributing/stable.rst > b/doc/guides/contributing/stable.rst > index d52ec4772..0f2f1f375 100644 > --- a/doc/guides/contributing/stable.rst > +++ b/doc/guides/contributing/stable.rst > @@ -42,10 +42,10 @@ LTS Release > ----------- > > A stable release can be designated as an LTS release based on community - > agreement and a commitment from a maintainer. An LTS release will have a - > maintenance duration of 2 years. > +agreement and a commitment from a maintainer. The current policy is > +that each year's November release will be maintained as an LTS for 2 > years. Strictly speaking we didn't agree that at Userspace. We said that we would evaluate a 18.11 release next year. However, I am okay with this statement since it probably reflects what the reality will be. Acked-by: John McNamara <john.mcnamara@intel.com>
> > Signed-off-by: Luca Boccassi <bluca@debian.org> > > --- [...] > > A stable release can be designated as an LTS release based on community - > > agreement and a commitment from a maintainer. An LTS release will have a - > > maintenance duration of 2 years. > > +agreement and a commitment from a maintainer. The current policy is > > +that each year's November release will be maintained as an LTS for 2 > > years. > > Strictly speaking we didn't agree that at Userspace. We said that we would evaluate > a 18.11 release next year. However, I am okay with this statement since it probably > reflects what the reality will be. > > Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net> Applied, thanks
diff --git a/doc/guides/contributing/stable.rst b/doc/guides/contributing/stable.rst index d52ec4772..0f2f1f375 100644 --- a/doc/guides/contributing/stable.rst +++ b/doc/guides/contributing/stable.rst @@ -42,10 +42,10 @@ LTS Release ----------- A stable release can be designated as an LTS release based on community -agreement and a commitment from a maintainer. An LTS release will have a -maintenance duration of 2 years. +agreement and a commitment from a maintainer. The current policy is that each +year's November release will be maintained as an LTS for 2 years. -The current DPDK LTS release is 16.11. +The current DPDK LTS releases are 16.11 and 17.11. It is anticipated that there will be at least 4 releases per year of the LTS or approximately 1 every 3 months. However, the cadence can be shorter or