> I agree there is a big need for that. Currently reviewing all the patches I haven't
> read (only 1000 mails to go...) to see if they need to be backported on top on
> rdma-core 15 for the next SLES.
> I'd gladly help maintaining this as I'm spending time on it anyway.
> I'll leave wiser people debate and ready a doc on how this should be done
> though :)
>
> Nicolas
Thanks Nicolas.
Ok, I am not sure what details the rdma-core maintainers are looking for in a document. Let me start the discussion with the following:
Stable Branch Release
Current Maintainer: Nicolas Morey-Chaisemartin <NMoreyChaisemartin@xxxxxxx>
Upstream rdma-core is considered stable after each mainline release. Branched stable releases, off a mainline release, are on as-needed basis and limited to bug fixes. All bug fixes are to be backported from mainline and applied by stable branch maintainer. Branched stable releases will append an additional release number (e.g. 15.1) and will ensure that Travis CI reports a successful build. Mention the frequency of stable releases or keep it "as is" cadence?
See versioning.md for setting package version on a stable branch.
Arlin
��.n��������+%������w��{.n�����{���fk��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
