From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>, Ali Alnubani <alialnu@nvidia.com>
Cc: "Morten Brørup" <mb@smartsharesystems.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] code.dpdk.org bugfix releases
Date: Fri, 4 Jun 2021 09:00:34 +0200 [thread overview]
Message-ID: <CAJFAV8y=x_LARSDjn0nNm0W-LE8=a8iANcdrtSCgT+e5K=LHfg@mail.gmail.com> (raw)
In-Reply-To: <1835865.ogO8Tvl0ac@thomas>
On Thu, Jun 3, 2021 at 9:18 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 03/06/2021 20:15, Morten Brørup:
> > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> > > Sent: Thursday, 3 June 2021 18.11
> > >
> > > 03/06/2021 17:18, Morten Brørup:
> > > > Hi all,
> > > >
> > > > Bugfix releases are missing on code.dpdk.org.
> > > >
> > > > E.g. version 17.11 is present, but version 17.11.10 is missing.
> > > >
> > > > Can whoever is the maintainer of code.dpdk.org please fix this.
> > >
> > > Ali is the admin of dpdk.org.
> > > I'm not sure your request is easy because stable releases
> > > are in a separate repository dpdk-stable.git.
> >
> > Ali, it would be great if you can include them.
> > Not having easy access to browse the source code of the LTS
> > bugfix releases could be a barrier for DPDK users to upgrade
> > to the latest LTS bugfix release.
>
> Actually it's already included (thanks Ali for reminding it to me):
> https://code.dpdk.org/dpdk-stable/v20.11/source
>
> There are 2 different repos and that's how it is exposed in this tool.
> It may be a bit confusing.
> Do you think it would be OK to rename dpdk-stable to dpdk in this tool?
If we do this, in the current state, we lose the non-stable branches.
19.02 and 19.05 (at least) are not present in the dpdk-stable part.
http://code.dpdk.org/dpdk-stable/v19.11.8/source
Not sure how to fix this, do we simply need to push release tags to dpdk-stable?
--
David Marchand
next prev parent reply other threads:[~2021-06-04 7:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 15:18 [dpdk-dev] code.dpdk.org bugfix releases Morten Brørup
2021-06-03 16:10 ` Thomas Monjalon
2021-06-03 18:15 ` Morten Brørup
2021-06-03 19:18 ` Thomas Monjalon
2021-06-03 19:36 ` Morten Brørup
2021-06-04 8:12 ` Thomas Monjalon
2021-06-04 8:19 ` Morten Brørup
2021-06-04 8:47 ` Thomas Monjalon
2021-06-04 9:14 ` Morten Brørup
2021-06-07 12:49 ` Ali Alnubani
2021-06-08 9:57 ` Morten Brørup
2021-06-08 10:23 ` Thomas Monjalon
2021-06-08 13:42 ` Luca Boccassi
2021-06-08 10:35 ` Kevin Traynor
2021-06-08 12:09 ` David Marchand
2021-06-04 7:00 ` David Marchand [this message]
2021-06-04 7:03 ` Morten Brørup
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='CAJFAV8y=x_LARSDjn0nNm0W-LE8=a8iANcdrtSCgT+e5K=LHfg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=alialnu@nvidia.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.