From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: rdma-core stable releases Date: Mon, 13 Nov 2017 12:16:25 -0700 Message-ID: <20171113191625.GH6918@ziepe.ca> References: <20171106182756.GD18802@ziepe.ca> <6012d1c3-cd18-25e8-c5ae-3d678142177b@suse.de> <54347E5A035A054EAE9D05927FB467F9B61778A9@ORSMSX101.amr.corp.intel.com> <20171110202455.GP18825@mtr-leonro.local> <20171113081455.GD18825@mtr-leonro.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20171113081455.GD18825-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Leon Romanovsky Cc: Nicolas Morey-Chaisemartin , "Davis, Arlin R" , "Kalderon, Michal" , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Doug Ledford , "Elior, Ariel" , "Rahman, Ameen" , "Amrani, Ram" , "Radzi, Amit" List-Id: linux-rdma@vger.kernel.org On Mon, Nov 13, 2017 at 10:14:55AM +0200, Leon Romanovsky 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. I would say anything that makes this job easier and more robust is a good idea. If tracking things on github makes sense for the involved parties then go for it. IHMO We do not really have the scale to warrent building a huge amount of custome automatic infrastructure.. 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