From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] version: 20.05-rc0
Date: Thu, 27 Feb 2020 11:17:18 +0000 [thread overview]
Message-ID: <20200227111718.GA1587@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CAJFAV8y+FSMM3VBBdVf0GeOc47mCtgo=LuqSOAqYROjHLP_S7w@mail.gmail.com>
On Wed, Feb 26, 2020 at 03:01:04PM +0100, David Marchand wrote:
> On Wed, Feb 26, 2020 at 2:55 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > 26/02/2020 14:38, David Marchand:
> > > Start a new release cycle with empty release notes.
> > > ABI must now be checked with v20.02 as a reference.
> > >
> > > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > > ---
> > > .travis.yml | 4 +
> > > ABI_VERSION | 2 +-
> > > VERSION | 2 +-
> > > doc/guides/rel_notes/index.rst | 1 +
> > > doc/guides/rel_notes/release_20_05.rst | 139 +++++++++++++++++++++++++
> > > 5 files changed, 146 insertions(+), 2 deletions(-)
> > > create mode 100644 doc/guides/rel_notes/release_20_05.rst
> >
> > Acked-by: Thomas Monjalon <thomas@monjalon.net>
> >
> >
> > > --- a/.travis.yml
> > > +++ b/.travis.yml
> > > +env:
> > > + global:
> > > + - REF_GIT_TAG=v20.02
> >
> > One question: why REF_GIT_TAG was not needed in Travis during 20.02?
>
> The .ci/linux-build.sh script has a default value for parameters.
> http://git.dpdk.org/dpdk/tree/.ci/linux-build.sh#n71&h=v20.02
>
> This could be removed, so that we only have explicit values in the
> .travis.yml configuration.
> No strong opinion keeping them.
>
Why do we need to update the git ref tag at all. Since these releases are
all ABI compatible with each other, can we not leave the checks still to be
against 19.11?
next prev parent reply other threads:[~2020-02-27 11:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 13:38 David Marchand
2020-02-26 13:55 ` Thomas Monjalon
2020-02-26 14:01 ` David Marchand
2020-02-27 11:17 ` Bruce Richardson [this message]
2020-02-27 11:23 ` David Marchand
2020-02-27 11:26 ` Thomas Monjalon
2020-02-27 11:01 ` David Marchand
2020-02-27 11:31 ` 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=20200227111718.GA1587@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).