DPDK website maintenance
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org, dev <dev@dpdk.org>,
	techboard@dpdk.org,  Luca Boccassi <bluca@debian.org>,
	Yuanhan Liu <yliu@fridaylinux.org>,
	 Kevin Traynor <ktraynor@redhat.com>,
	yskoh@mellanox.com
Subject: Re: [dpdk-web] [PATCH v2] update stable releases roadmap
Date: Wed, 11 Apr 2018 12:43:35 +0200	[thread overview]
Message-ID: <CAATJJ0J2-EeEUmjYQxLayy-VFb2au8pU5YojUc+wEnYUC3nUEg@mail.gmail.com> (raw)
In-Reply-To: <20180410232813.2534-1-thomas@monjalon.net>

On Wed, Apr 11, 2018 at 1:28 AM, Thomas Monjalon <thomas@monjalon.net>
wrote:

> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> Patch for the website (to web@dpdk.org) Cc'ed to dev@dpdk.org
>
> v2:
>         - more volunteers
>         - propose to do .1 release after -rc1 of next branch.
>
> ---
>  dev/roadmap.html | 37 ++++++++++++++++++++++++++++++++-----
>  1 file changed, 32 insertions(+), 5 deletions(-)
>
> [...]
> +               <tr>
> +                       <td>18.05.1</td>
> +                       <td>June 29, 2018</td>
> +                       <td>October 2018</td>
> +                       <td>Christian Ehrhardt</td>
> +               </tr>
>

Acked-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>

  parent reply	other threads:[~2018-04-11 10:44 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09 13:36 [dpdk-web] [PATCH] " Thomas Monjalon
2018-03-09 13:44 ` Luca Boccassi
2018-03-09 13:49   ` Thomas Monjalon
2018-03-09 14:03     ` [dpdk-web] [dpdk-techboard] " Ananyev, Konstantin
2018-03-09 14:19       ` Thomas Monjalon
2018-03-09 15:24         ` Ferruh Yigit
2018-03-09 15:45           ` Thomas Monjalon
2018-03-09 17:30             ` Luca Boccassi
2018-03-09 14:30 ` [dpdk-web] " Kevin Traynor
2018-03-09 14:51   ` Thomas Monjalon
2018-03-09 15:43     ` Kevin Traynor
2018-03-22 11:03 ` Luca Boccassi
2018-03-22 11:22   ` Luca Boccassi
2018-03-22 11:25   ` Thomas Monjalon
     [not found] ` <1522937784.16877.28.camel@debian.org>
2018-04-05 14:19   ` Christian Ehrhardt
2018-04-05 14:23     ` Thomas Monjalon
2018-04-10 23:28 ` [dpdk-web] [PATCH v2] " Thomas Monjalon
2018-04-11 10:04   ` Luca Boccassi
2018-04-11 10:43   ` Christian Ehrhardt [this message]
2018-04-11 15:10   ` Kevin Traynor
2018-04-18  9:05   ` Ferruh Yigit
2018-04-18  9:14     ` Thomas Monjalon
2018-04-18 12:28       ` Ferruh Yigit
2018-04-18 13:28         ` Thomas Monjalon
2018-04-19  9:38           ` Kevin Traynor
2018-04-20 15:52             ` [dpdk-web] [dpdk-dev] " Aaron Conole
2018-04-25  8:33               ` Ferruh Yigit
2018-04-25 10:03                 ` Luca Boccassi
2018-04-30 10:47                   ` Thomas Monjalon
2018-05-01 14:16                     ` Aaron Conole
2018-05-01 15:46                       ` Kevin Traynor
2018-05-01 16:02                         ` Thomas Monjalon
2018-05-17 16:32 ` [dpdk-web] [PATCH v3] " Thomas Monjalon
2018-05-17 16:41   ` Ferruh Yigit
2018-05-17 16:59     ` Thomas Monjalon

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=CAATJJ0J2-EeEUmjYQxLayy-VFb2au8pU5YojUc+wEnYUC3nUEg@mail.gmail.com \
    --to=christian.ehrhardt@canonical.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=ktraynor@redhat.com \
    --cc=techboard@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=web@dpdk.org \
    --cc=yliu@fridaylinux.org \
    --cc=yskoh@mellanox.com \
    /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).