Signed-off-by: Kevin Traynor <ktraynor@redhat.com> --- content/roadmap/_index.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md index 9d3f8e6..a07ed2b 100644 --- a/content/roadmap/_index.md +++ b/content/roadmap/_index.md @@ -127,6 +127,8 @@ After each -rc tag and after the final version, relevant bug fixes get backported by the stable maintainers into the respective branches in "bursts". -Developers can provide stable-specific patches by sending them -to stable@dpdk.org only (avoiding dev@dpdk.org). +Developers can provide stable specific patches by sending them +to stable@dpdk.org only (avoiding dev@dpdk.org). Further information on +subject prefixes for this case is documented +[here](//doc.dpdk.org/guides/contributing/patches.html#backporting-patches-for-stable-releases). After all the relevant bugfixes have been backported, @@ -134,5 +136,5 @@ regression tests are run, and if clear, the stable release is announced. Typically a new stable release version follows a mainline release -by 1-2 weeks, depending on the test results. +by 3-6 weeks, depending on the test results. | Current version | Next version | Next version Date | End of life | Maintainers | -- 2.31.1
Add initial dates and maintainer for 21.11 LTS as approved by Techboard in http://mails.dpdk.org/archives/dev/2021-December/230920.html Signed-off-by: Kevin Traynor <ktraynor@redhat.com> --- content/roadmap/_index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md index a07ed2b..5f7a767 100644 --- a/content/roadmap/_index.md +++ b/content/roadmap/_index.md @@ -143,2 +143,3 @@ by 3-6 weeks, depending on the test results. | 19.11.11 | 19.11.12 | May 2022 | December 2022 (LTS) | Christian Ehrhardt | | 20.11.3 | 20.11.4 | December 2021 | November 2022 (LTS) | Luca Boccassi, Xueming Li | +| 21.11.0 | 21.11.1 | April 2022 | November 2023 (LTS) | Kevin Traynor | -- 2.31.1
11/01/2022 13:19, Kevin Traynor:
> Add initial dates and maintainer for 21.11 LTS
> as approved by Techboard in
> http://mails.dpdk.org/archives/dev/2021-December/230920.html
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> ---
> +| 21.11.0 | 21.11.1 | April 2022 | November 2023 (LTS) | Kevin Traynor |
Acked-by: Thomas Monjalon <thomas@monjalon.net>
Thanks for volunteering
11/01/2022 13:19, Kevin Traynor: > Signed-off-by: Kevin Traynor <ktraynor@redhat.com> > --- > content/roadmap/_index.md | 8 +++++--- > 1 file changed, 5 insertions(+), 3 deletions(-) > > diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md > index 9d3f8e6..a07ed2b 100644 > --- a/content/roadmap/_index.md > +++ b/content/roadmap/_index.md > @@ -127,6 +127,8 @@ After each -rc tag and after the final version, relevant bug fixes get > backported by the stable maintainers into the respective branches in "bursts". > > -Developers can provide stable-specific patches by sending them > -to stable@dpdk.org only (avoiding dev@dpdk.org). > +Developers can provide stable specific patches by sending them > +to stable@dpdk.org only (avoiding dev@dpdk.org). Further information on Please start sentence on a new line. > +subject prefixes for this case is documented > +[here](//doc.dpdk.org/guides/contributing/patches.html#backporting-patches-for-stable-releases). > > After all the relevant bugfixes have been backported, > @@ -134,5 +136,5 @@ regression tests are run, and if clear, the stable release is announced. > > Typically a new stable release version follows a mainline release > -by 1-2 weeks, depending on the test results. > +by 3-6 weeks, depending on the test results.
On 11/01/2022 12:43, Thomas Monjalon wrote: > 11/01/2022 13:19, Kevin Traynor: >> Signed-off-by: Kevin Traynor <ktraynor@redhat.com> >> --- >> content/roadmap/_index.md | 8 +++++--- >> 1 file changed, 5 insertions(+), 3 deletions(-) >> >> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md >> index 9d3f8e6..a07ed2b 100644 >> --- a/content/roadmap/_index.md >> +++ b/content/roadmap/_index.md >> @@ -127,6 +127,8 @@ After each -rc tag and after the final version, relevant bug fixes get >> backported by the stable maintainers into the respective branches in "bursts". >> >> -Developers can provide stable-specific patches by sending them >> -to stable@dpdk.org only (avoiding dev@dpdk.org). >> +Developers can provide stable specific patches by sending them >> +to stable@dpdk.org only (avoiding dev@dpdk.org). Further information on > > Please start sentence on a new line. > Ack, thanks. Will wait to see if there's any other comments, then send a v2. >> +subject prefixes for this case is documented >> +[here](//doc.dpdk.org/guides/contributing/patches.html#backporting-patches-for-stable-releases). >> >> After all the relevant bugfixes have been backported, >> @@ -134,5 +136,5 @@ regression tests are run, and if clear, the stable release is announced. >> >> Typically a new stable release version follows a mainline release >> -by 1-2 weeks, depending on the test results. >> +by 3-6 weeks, depending on the test results. > > >
Signed-off-by: Kevin Traynor <ktraynor@redhat.com> --- content/roadmap/_index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md index 9d3f8e6..cf212a4 100644 --- a/content/roadmap/_index.md +++ b/content/roadmap/_index.md @@ -129,4 +129,6 @@ backported by the stable maintainers into the respective branches in "bursts". Developers can provide stable-specific patches by sending them to stable@dpdk.org only (avoiding dev@dpdk.org). +Further information on subject prefixes for this case is documented +[here](//doc.dpdk.org/guides/contributing/patches.html#backporting-patches-for-stable-releases). After all the relevant bugfixes have been backported, @@ -134,5 +136,5 @@ regression tests are run, and if clear, the stable release is announced. Typically a new stable release version follows a mainline release -by 1-2 weeks, depending on the test results. +by 3-6 weeks, depending on the test results. | Current version | Next version | Next version Date | End of life | Maintainers | -- 2.31.1
Add initial dates and maintainer for 21.11 LTS as approved by Techboard in http://mails.dpdk.org/archives/dev/2021-December/230920.html Signed-off-by: Kevin Traynor <ktraynor@redhat.com> Acked-by: Thomas Monjalon <thomas@monjalon.net> --- content/roadmap/_index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md index cf212a4..326173a 100644 --- a/content/roadmap/_index.md +++ b/content/roadmap/_index.md @@ -143,2 +143,3 @@ by 3-6 weeks, depending on the test results. | 19.11.11 | 19.11.12 | May 2022 | December 2022 (LTS) | Christian Ehrhardt | | 20.11.3 | 20.11.4 | December 2021 | November 2022 (LTS) | Luca Boccassi, Xueming Li | +| 21.11.0 | 21.11.1 | April 2022 | November 2023 (LTS) | Kevin Traynor | -- 2.31.1
On 13/01/2022 10:19, Kevin Traynor wrote:
> Add initial dates and maintainer for 21.11 LTS
> as approved by Techboard in
> http://mails.dpdk.org/archives/dev/2021-December/230920.html
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> Acked-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> content/roadmap/_index.md | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
> index cf212a4..326173a 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -143,2 +143,3 @@ by 3-6 weeks, depending on the test results.
> | 19.11.11 | 19.11.12 | May 2022 | December 2022 (LTS) | Christian Ehrhardt |
> | 20.11.3 | 20.11.4 | December 2021 | November 2022 (LTS) | Luca Boccassi, Xueming Li |
> +| 21.11.0 | 21.11.1 | April 2022 | November 2023 (LTS) | Kevin Traynor |
I applied these as there is some incoming questions about LTS versions.
Thanks.