Re: rdma-core stable releases

[Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>]

[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]

On Mon, Nov 13, 2017 at 08:18:02AM +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 > >
> The only issue I can foresee with these is that we need to run the ABI checker on both the "old" and "new" versions.
> We would probably need to do something at release time to generate and publish the ABI xml file somewhere (either in the repo, or github) so that we can check against it later without recompiling it.

We can publish it together with released files in github release section.

Thanks

>
> Nicolas
>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]