ANNOUNCE - New release of rdma-core
The final upstream release of version 12 of the rdma-core package has been tagged and pushed to github.
This marks the first official release of the rdma-core package, and also the first release of libibverbs not to be hosted on kernel.org and openfabrics.org.
For the libibverbs git repo, I have deleted all of its contents and left behind a README file to point people to the new rdma-core repo on github. I would suggest maintainers of the other components pulled into rdma-core do the same thing. I did a similar thing in the download area for verbs, modifying the README file to let people know about the new package.
This also marks a new means of verifying the contents of releases. Unlike tarballs with uploaded sha1sums or the like, we are using the git tag mechanism to uniquely identify the code that makes up a release. If you don't see a validated PGP signature on the tag, then don't trust it. The github interface makes it easy to tell if a given release is verified as it throws a "Verified" badge up on the release when it is PGP signed. You can then download either a zip or tar.gz file from the github release. I don't know if the contents of that tarball are subject to minor changes (such as file ordering, or access timestamps), so a tarball sha1sum is not necessarily even possible when using the git repo tag mechanism to denote releases. However, the git scm in general makes tags so reliable that this should not be a concern to anyone.
The release is version 12, and the tag is:
tag rdma-core-12
Tagger: Doug Ledford <[email protected]> Date: Tue Jan 17 14:17:36 2017 -0500
This is the final version 12 release of rdma-core
- Merge all upstream sources into the single rdma-core package
- Provide nice packaging for RPM and Debian based systems
- First release of combined package, targetting the 4.9 kernel as a matched release. This package will work with other kernels, but fully supports all of the features in the 4.9 kernel.
- Move upstream to github
- Add libqedr provider
- Add libi40iw provider
- Add librxe (SoftRoCE) provider
- Add libhns provider
- Straighten out copyright files and make license consistent across source code portions
- Introduce flow steering improvements
- Replace code taken from linux kernel (and possibly under the GPL, even
though at least some of it seemed to possibly be not copyrightable due
to the Merger Doctrine) with undoubtedly license compatible CCAN code (list.h and a few other minor library type code bases)
- Drop use of autotools for building and libtool for library building and instead use CMake and ninja build tools
-----BEGIN PGP SIGNATURE----- iQIcBAABAgAGBQJYfm/RAAoJELgmozMOVy/doBMP/jyqxfkUd/eweDIeUHX7werD l16cT3hHNHUx2T0XnGejT0UTSQgUKDbO6WLOg3+1bC2uKY7Cue0bmV5+VYbs53i8 Q8ifMiARXZKQwR0Q4XI504T0cTkwHYw+y6nzG35exs7dp2rtAclL5gM/YfaonbPs G38VUV3v4m4+1BpIgMSg7YQngtALVT9uyLjHYv7ppXu1sKCQJ92uaLQfGhvGM4aA sWDDODJt+mxC2scg0eU1Fy170edc13+styjRk8SXdRk02c6XWDMyKZ8USzN5Gwvq QoMhxlia/+qzO1LFOcrNLP7AJMYQ1o+fho6yJQoP94EqdFVwNicgt38FGaHJ5aKw tVVBe7hVHLtJLXrh+G2RBvHuFeQ8/w319QQxTExQYPJ37nnPF4vL8OnyOketntET +z11Yxa8Jx8gTf+qvv0f7HlWhdtu5rJOUNW19u8vnyrgvFsFwTQcVDDqJsQSK0xS 6gtx3dZc9NpLQtFEIHkZSXUV8FD82GHeFqkLJ1Ee+MR68Tp4/7g0ZHdIwsV/dU1D kzbdWVnVVWCzJhbEdABl3loNzazD5BIzhrm+C9v69X86hGbGPQY4Wct9izCWk0VP Y2BuAyMoPeanXssak0n9Bd8dYcKbtVQdg9ijAIiOjoDbyxFmLpY1N0PVXv84o7L8 lqzBuqC1aZOWtqS7CJGV
=6REJ
-----END PGP SIGNATURE-----
commit 26398cbf74de32f622ae86ad4cbfa6a3792ba616
Merge: fc645ff22e54 5fc5b4e26307
Author: Leon Romanovsky <[email protected]> Date: Tue Jan 17 16:00:14 2017 +0200
Merge pull request #54 from bdrung/master
debian: Improve packaging
Signature · 4 lines
Doug Ledford <[email protected]> GPG KeyID: B826A3330E572FDD Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
Quoted 6 lines · Doug Ledford
The final upstream release of version 12 of the rdma-core package has been tagged and pushed to github.
This marks the first official release of the rdma-core package, and also the first release of libibverbs not to be hosted on kernel.org and openfabrics.org.
So where is it hosted? I don't see any link to a tarball.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 6 lines · Christoph Hellwig
Quoted 5 lines · Doug Ledford
The final upstream release of version 12 of the rdma-core package has
been tagged and pushed to github.
Quoted 6 lines
Quoted 4 lines
This marks the first official release of the rdma-core package, and also the first release of libibverbs not to be hosted on kernel.org and
openfabrics.org.So where is it hosted? I don't see any link to a tarball.
It's on github. When viewing the repo, click on the "Releases" tab above the code listing, there you will find the list of releases, and under each one there is a link to either a zip or tgz download. As has been pointed out, the internal directory structure of the release tarball is wonky on this one. Still working that out...
Signature · 4 lines
Doug Ledford <[email protected]> GPG KeyID: B826A3330E572FDD Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
Quoted 5 lines · Doug Ledford
It's on github. When viewing the repo, click on the "Releases" tab above the code listing, there you will find the list of releases, and under each one there is a link to either a zip or tgz download. As has been pointed out, the internal directory structure of the release tarball is wonky on this one. Still working that out...
I would be nice to include a link to it next time a release is cut. --
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 9 lines · Christoph Hellwig
Quoted 5 lines · Doug Ledford
It's on github. When viewing the repo, click on the "Releases" tab above the code listing, there you will find the list of releases, and under each one there is a link to either a zip or tgz download. As has been pointed out, the internal directory structure of the release tarball is wonky on this one. Still working that out...
I would be nice to include a link to it next time a release is cut.
Sure, I'll add that to my list of things to get working better with the release process on github ;-)
Signature · 3 lines
Doug Ledford <[email protected]> GPG Key ID: B826A3330E572FDD Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD