Re: rdma-core stable releases

Nicolas Morey-Chaisemartin
2017-11-13T09:16:32Z

Le 13/11/2017 à 09:14, Leon Romanovsky a écrit :
> On Mon, Nov 13, 2017 at 08:53:19AM +0100, Nicolas Morey-Chaisemartin wrote:
>>
>> What would make sense IMHO would be to have people submit their patches to stable branches through a github issues.
>> Each issue should be tagged in all the main/stable release it is in and contains a SHA1 to a patch from master that contains a fix.
>>
> I personally against such close integration with github and creating two
> different places for communication (ML and github), but as Jason said,
> the core team has no plans to manage it and it will be your decision on
> how you will manage it.
>
> Right now, the gihtub issues are disabled in rdma-core, because we
> didn't want people open bug reports there instead of posting to the ML.
>
> Thanks

I just saw that on Github. And yes people will open bug for master there.
I don't want to intrude in  your workflow..

I'm OK with keeping just the ML for the moment. If it becomes too much of a mess, I'll come back with my github request (or something else).
How do you suggest flagging me for those patches ? Should we follow the kernel stable process ?
Meaning either:
- CC me with version information on a submission to master
- Send a mail to ML + me after patch has been accepted in master with a tag like [PATCH rdma-core stable], a list of patch-id from master, the version they apply to and why they should be picked

Do you have any request/idea/suggestion about the release rate of the stable branch ?

Nicolas