Re: rdma-core stable releases

[Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>]

On Tue, Nov 14, 2017 at 01:05:58PM +0200, Leon Romanovsky wrote:
> On Tue, Nov 14, 2017 at 11:27:40AM +0100, Nicolas Morey-Chaisemartin wrote:
> >
> >
> > Le 13/11/2017 à 08:08, Leon Romanovsky a écrit :
> > > On Mon, Nov 13, 2017 at 08:01:48AM +0100, Nicolas Morey-Chaisemartin wrote: >> >> >> Le 10/11/2017 à 22:14, Jason Gunthorpe a écrit : >>> On Fri, Nov 10, 2017 at 10:24:55PM +0200, Leon Romanovsky wrote: >>>> More or less, you wrote everything that I expected, just need to post it >>>> as a patch so I can apply it to rdma-core. >>> Also please describe how to get patches into -stable, eg similar to >>> the kernel, mark with fixes and cc the stable maintainer. >>> >>> There should also be absolutely no ABI changes in the -stable branchs. >> >> Agreed. Ideally we would add something to CI so that it detects ABI breake on stable branches. >> I know SUSE has something like this for maintenance fixes. I'll look into it. > > DPDK runs ABI compliance checker. > http://ispras.linuxbase.org/
 index.php/ABI_compliance_checker > > I would love to see it running for rdma-core. > > Thanks >
> > Got the scripts ready for this BUT the versions available in docker of abi-dump/abi-compliance-checker are not compatible.
> > As both are GPLv2, could I import them into buildlib ?
> 
> I'm not a lawyer, Our dual license policy is relevant for source
> code and build scripts only. The tools for our CI can be GPLv2-only.

Right, but it is very important that any important code come with the
right license files in COPYING.* so you'd have to at least add
COPYING.LGPL and update debian/copyright and COPYING.md

The files look small enough that we could choose to include them in
buildlib.

Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html