From: Thomas Monjalon <thomas@monjalon.net>
To: Luca Boccassi <Luca.Boccassi@microsoft.com>,
"ktraynor@redhat.com" <ktraynor@redhat.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Cc: "web@dpdk.org" <web@dpdk.org>
Subject: Re: [dpdk-web] [PATCH v2] update stable tree schedules
Date: Tue, 25 Jun 2019 16:05:55 +0200 [thread overview]
Message-ID: <34700841.xdIFGKGpnP@xps> (raw)
In-Reply-To: <e93041915aae015d3aabf03fc6e827d3cb3a0abb.camel@microsoft.com>
25/06/2019 16:00, Luca Boccassi:
> On Tue, 2019-06-25 at 15:41 +0200, Thomas Monjalon wrote:
> > From: Ferruh Yigit <
> > ferruh.yigit@intel.com
> > >
> >
> > There is a date level detail for the future stable release dates,
> > which
> > are mostly not correct because they are far away to know this detail.
> > Removing the date detail from the stable release dates and keeping
> > only
> > month of the year as the release target.
> >
> > By default putting the next month of the actual release as target for
> > stable version release.
> >
> > Unmaintained branches are removed. 19.02.1 will never happen.
> >
> > Signed-off-by: Ferruh Yigit <
> > ferruh.yigit@intel.com
> > >
> > Signed-off-by: Thomas Monjalon <
> > thomas@monjalon.net
> > >
> > Acked-by: Luca Boccassi <
> > luca.boccassi@microsoft.com
> > >
> > Acked-by: Kevin Traynor <
> > ktraynor@redhat.com
> > >
>
> Acked-by: Luca Boccassi <luca.boccassi@microsoft.com>
Applied, thanks
next prev parent reply other threads:[~2019-06-25 14:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 16:42 [dpdk-web] [PATCH 1/2] update 18.11.2 schedule Ferruh Yigit
2019-05-16 16:42 ` [dpdk-web] [PATCH 2/2] update stable tree schedules Ferruh Yigit
2019-05-16 16:48 ` Luca Boccassi
2019-05-16 17:15 ` Kevin Traynor
2019-06-25 13:41 ` [dpdk-web] [PATCH v2] " Thomas Monjalon
2019-06-25 14:00 ` Luca Boccassi
2019-06-25 14:05 ` Thomas Monjalon [this message]
2019-05-16 17:12 ` [dpdk-web] [PATCH 1/2] update 18.11.2 schedule Kevin Traynor
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=34700841.xdIFGKGpnP@xps \
--to=thomas@monjalon.net \
--cc=Luca.Boccassi@microsoft.com \
--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).