DPDK website maintenance
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Luca Boccassi <bluca@debian.org>,
	Kevin Traynor <ktraynor@redhat.com>,
	web@dpdk.org
Cc: thomas@monjalon.net, david.marchand@redhat.com
Subject: Re: [dpdk-web] [PATCH] release 18.11.10
Date: Mon, 28 Sep 2020 15:55:12 +0100	[thread overview]
Message-ID: <d12c41f1-70bd-27b4-52e1-9eec0bed58d2@intel.com> (raw)
In-Reply-To: <4284365f1087262026b14221383410571d7b42d6.camel@debian.org>

On 9/28/2020 3:53 PM, Luca Boccassi wrote:
> On Mon, 2020-09-28 at 15:35 +0100, Kevin Traynor wrote:
>> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
>> ---
>>   content/download/_index.md | 2 +-
>>   content/roadmap/_index.md  | 2 +-
>>   2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/content/download/_index.md b/content/download/_index.md
>> index 2b87f8e..e0bb061 100644
>> --- a/content/download/_index.md
>> +++ b/content/download/_index.md
>> @@ -33,5 +33,5 @@ weight = "2"
>>   | [DPDK 19.05.0](//fast.dpdk.org/rel/dpdk-19.05.tar.xz)         | [2019 May 13](//doc.dpdk.org/guides-19.05/rel_notes/release_19_05.html)      | fe22ad1bab1539945119047b0fdf1105 |
>>   | [DPDK 19.02.0](//fast.dpdk.org/rel/dpdk-19.02.tar.xz)         | [2019 February 1](//doc.dpdk.org/guides-19.02/rel_notes/release_19_02.html)  | 23944a2cdee061aa4bd72ebe7d836db0 |
>> -| [DPDK 18.11.9 (LTS)](//fast.dpdk.org/rel/dpdk-18.11.9.tar.xz) | [2020 July 10](//doc.dpdk.org/guides-18.11/rel_notes/release_18_11.html)     | 84fea30b4007e4eb15102f62c55e71c8 |
>> +| [DPDK 18.11.10 (LTS)](//fast.dpdk.org/rel/dpdk-18.11.10.tar.xz) | [2020 September 28](//doc.dpdk.org/guides-18.11/rel_notes/release_18_11.html)     | a97a33bda610feb891dc9e1e418a8fe6 |
>>   | [DPDK 18.08.1](//fast.dpdk.org/rel/dpdk-18.08.1.tar.xz)       | [2019 April 1](//doc.dpdk.org/guides-18.08/rel_notes/release_18_08.html)     | 391116ff3012ffd33bb63ed5feb3375c |
>>   | [DPDK 18.05.1](//fast.dpdk.org/rel/dpdk-18.05.1.tar.xz)       | [2018 Sept 7](//doc.dpdk.org/guides-18.05/rel_notes/release_18_05.html)      | 5e278012506c76d981e4283a92adec1c |
>> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
>> index 2bea48f..5dbe5dd 100644
>> --- a/content/roadmap/_index.md
>> +++ b/content/roadmap/_index.md
>> @@ -118,4 +118,4 @@ by 1-2 weeks, depending on the test results.
>>   | Current version | Next version  | Next version Date | End of life | Maintainer     |
>>   |----------|----------|-------------------|---------------------|--------------------|
>> -| 18.11.9  | 18.11.10 | September 2020    | November 2020 (LTS) | Kevin Traynor      |
>> +| 18.11.10 | 18.11.11 | December 2020     | December 2020 (LTS) | Kevin Traynor      |
>>   | 19.11.5  | 19.11.6  | December 2020     | November 2021 (LTS) | Luca Boccassi      |
> 
> Acked-by: Luca Boccassi <bluca@debian.org>
> 

Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>

      reply	other threads:[~2020-09-28 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28 14:35 Kevin Traynor
2020-09-28 14:53 ` Luca Boccassi
2020-09-28 14:55   ` Ferruh Yigit [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d12c41f1-70bd-27b4-52e1-9eec0bed58d2@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bluca@debian.org \
    --cc=david.marchand@redhat.com \
    --cc=ktraynor@redhat.com \
    --cc=thomas@monjalon.net \
    --cc=web@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).