DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Luca Boccassi <bluca@debian.org>
Cc: web@dpdk.org, yliu@fridaylinux.org, ktraynor@redhat.com,
	techboard@dpdk.org, john.mcnamara@intel.com
Subject: Re: [dpdk-web] [PATCH] update stable releases roadmap
Date: Thu, 22 Mar 2018 12:25:12 +0100	[thread overview]
Message-ID: <101469652.poQfFCCKWp@xps> (raw)
In-Reply-To: <1521716595.14111.56.camel@debian.org>

22/03/2018 12:03, Luca Boccassi:
> Hi,
> 
> I'm happy to help with 18.02.1.

Thanks a lot.
For next stable branches, we must find more volunteers.

> Given it will be based on 18.05-rc2, which is due out on approximately
> April 20th, I think we can be ambitious and target April 27th as the
> tentative release date.

I think 18.02.1 should be based on 18.05-rc1, so April 20th would be
a tentative release date for 18.02.1 (before 18.05-rc2).
I will send a v2 of this schedule.

> Note that ATT won't be able to help with regression tests this time
> around. John, may we count on help from Intel to run the usual batch of
> regression tests between the 20th and the 27th?

Or one week before :)

It would be good to have more companies involved in testing stable releases.
We need to explicitly ask to some of the members. Can be done privately.

  parent reply	other threads:[~2018-03-22 11:25 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09 13:36 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 [this message]
     [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
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=101469652.poQfFCCKWp@xps \
    --to=thomas@monjalon.net \
    --cc=bluca@debian.org \
    --cc=john.mcnamara@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=techboard@dpdk.org \
    --cc=web@dpdk.org \
    --cc=yliu@fridaylinux.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).