From: Madhan Sivakumar <madhans@microsoft.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Justin Parus <Justin.Parus@microsoft.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
"tdelanerolle@linuxfoundation.org"
<tdelanerolle@linuxfoundation.org>
Subject: Re: [dpdk-users] Suggestion: DPDK "latest" Download Links
Date: Thu, 23 Aug 2018 21:55:58 +0000 [thread overview]
Message-ID: <MWHPR21MB0848772547F4E9D229D18184BD370@MWHPR21MB0848.namprd21.prod.outlook.com> (raw)
In-Reply-To: <10660669.gPjk7PcmS0@xps>
Thomas, it would be super useful to have this in order to make sure the underlying platform is not broken with any version update. We don't expect code changes in application unless there is a breaking API change right? This would be good to identify it too as part of automation.
-----Original Message-----
From: users <users-bounces@dpdk.org> On Behalf Of Thomas Monjalon
Sent: Thursday, August 23, 2018 4:09 AM
To: Ferruh Yigit <ferruh.yigit@intel.com>; Justin Parus <Justin.Parus@microsoft.com>
Cc: users@dpdk.org; tdelanerolle@linuxfoundation.org
Subject: Re: [dpdk-users] Suggestion: DPDK "latest" Download Links
22/08/2018 11:58, Ferruh Yigit:
> On 8/20/2018 8:03 PM, Justin Parus wrote:
> > Hi,
> >
> > I would like to propose adding DPDK "latest" download links. For example dpdk-latest-major and dpdk-latest-stable, would automatically update and point to the most recent date major and stable releases respectively. This would be useful for our tests as they would always be testing the latest packages automatically.
>
> +1, looks good idea
I am not sure how useful it is.
When you change from one major version to another one, you often have to adapt your code, so it cannot be automatic.
I see more values in having a link for the latest version of each stable branch.
prev parent reply other threads:[~2018-08-23 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 19:03 Justin Parus
2018-08-22 9:58 ` Ferruh Yigit
[not found] ` <10660669.gPjk7PcmS0@xps>
2018-08-23 21:55 ` Madhan Sivakumar [this message]
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=MWHPR21MB0848772547F4E9D229D18184BD370@MWHPR21MB0848.namprd21.prod.outlook.com \
--to=madhans@microsoft.com \
--cc=Justin.Parus@microsoft.com \
--cc=ferruh.yigit@intel.com \
--cc=tdelanerolle@linuxfoundation.org \
--cc=thomas@monjalon.net \
--cc=users@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).