DPDK website maintenance
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Kevin Traynor <ktraynor@redhat.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	 web@dpdk.org
Subject: Re: [dpdk-web] [PATCH 2/2] release 20.02.1
Date: Mon, 18 May 2020 14:47:04 +0100	[thread overview]
Message-ID: <59cf01270930f19798e5cf6b6bd8b9f1645be424.camel@debian.org> (raw)
In-Reply-To: <09cc090b-cc4f-a326-df35-20493e6b1559@redhat.com>

On Mon, 2020-05-18 at 14:43 +0100, Kevin Traynor wrote:
> On 18/05/2020 14:38, Ferruh Yigit wrote:
> > On 5/18/2020 2:28 PM, Luca Boccassi wrote:
> > > Signed-off-by: Luca Boccassi <bluca@debian.org>
> > > ---
> > >  content/download/_index.md | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/content/download/_index.md
> > > b/content/download/_index.md
> > > index ceeb218..68e2570 100644
> > > --- a/content/download/_index.md
> > > +++ b/content/download/_index.md
> > > @@ -25,7 +25,7 @@ weight = "2"
> > >  
> > >  |
> > > file                                                          |
> > > date/changelog                                                   
> > >             | md5                              |
> > >  |---------------------------------------------------------------
> > > |--------------------------------------------------------------
> > > ----------------|----------------------------------|
> > > -| [DPDK 20.02.0](//fast.dpdk.org/rel/dpdk-
> > > 20.02.tar.xz)         | [2020 February 25](//doc.dpdk.org/guides-
> > > 20.02/rel_notes/release_20_02.html) |
> > > e20171462d6b2252dfbae1de8c45ba10 |
> > > +| [DPDK 20.02.1](//fast.dpdk.org/rel/dpdk-
> > > 20.02.1.tar.xz)       | [2020 May 18](//doc.dpdk.org/guides-
> > > 20.02/rel_notes/release_20_02.html)      |
> > > fd04cb05c728f474b438c6e7aa1eb195 |
> > >  | [DPDK 19.11.1 (LTS)](//fast.dpdk.org/rel/dpdk-19.11.2.tar.xz)
> > > | [2020 May 18](//doc.dpdk.org/guides-
> > > 19.11/rel_notes/release_19_11.html)      |
> > > cd59c6577073b0a7bdf038f2658df1f2 |
> > >  | [DPDK 19.08.2](//fast.dpdk.org/rel/dpdk-
> > > 19.08.2.tar.xz)       | [2019 November 15](//doc.dpdk.org/guides-
> > > 19.08/rel_notes/release_19_08.html) |
> > > 97e71f5fed2e5fa21aae16cae82f9e04 |
> > >  | [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 |
> > > 
> > 
> > Similar to 19.11.2 comment, may need to update 'Latest 20.02' link
> > too.
> > 
> > Also since there is a 20.02.1 release, should we add this into the
> > roadmap table?
> > 
> I don't think so, there is not a roadmap to give it more releases

Yes, there are no plans for more. Pushed with suggested fixes.

-- 
Kind regards,
Luca Boccassi

  reply	other threads:[~2020-05-18 13:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18 13:28 [dpdk-web] [PATCH 1/2] release 19.11.2 Luca Boccassi
2020-05-18 13:28 ` [dpdk-web] [PATCH 2/2] release 20.02.1 Luca Boccassi
2020-05-18 13:38   ` David Marchand
2020-05-18 13:38   ` Ferruh Yigit
2020-05-18 13:43     ` Kevin Traynor
2020-05-18 13:47       ` Luca Boccassi [this message]
2020-05-18 13:32 ` [dpdk-web] [PATCH 1/2] release 19.11.2 Ferruh Yigit
2020-05-18 13:37   ` Ferruh Yigit
2020-05-18 13:37 ` David Marchand

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=59cf01270930f19798e5cf6b6bd8b9f1645be424.camel@debian.org \
    --to=bluca@debian.org \
    --cc=ferruh.yigit@intel.com \
    --cc=ktraynor@redhat.com \
    --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).