Sorry for the very late reply. I missed this thread completely.. There are no official rules at this point. I try to not go too much over 20 branches to maintain. Even if a lot of it is scripted, I still need to fix conflicts and build all thoses branches and click all over the place on Github to make releases. As rdma-core is released roughly every 2 months, 20 releases is over 3 years of support. Which is quite reasonable amount of time. The latest batch has 22 branches, but the oldests have seen some "significant" movement so I'm keeping them for now. If anyone has a good reason to keep a branch for longer (within reason), I'd be happy to. Also these decisions are not final. If needed, a branch can be brought back from the last to get a new stable releases. I would also accept PR and/or backported patches to these branches if Oracle has some needs I haven't met ;) Nicolas On 2024-01-25 11:25, Leon Romanovsky wrote: > On Wed, Jan 24, 2024 at 04:05:08PM -0600, Aron Silverton wrote: >> Hi Nicolas, >> >> What is the rule used to determine when older releases are no longer >> supported? Can something be added to Documentation/stable.md to explain? > > My guess is that it is Nicolas's desire to keep this list limited in size, > at the end he handles alone all rdma-core stables. > > ➜ rdma-core git:(master) ✗ git show v29.0 > tag v29.0 > .... > Date: Mon Apr 13 14:53:55 2020 +0300 > > v29 was released almost 4 years ago. > > Thanks > >> >> Thanks, >> >> Aron >> >> On Mon, Jan 22, 2024 at 07:33:36PM +0100, Nicolas Morey wrote: >>> These version were tagged/released: >>> * v29.12 => This will be it's last stable release >>> * v30.12 >>> * v31.13 >>> * v32.12 >>> * v33.12 >>> * v34.11 >>> * v35.10 >>> * v36.10 >>> * v37.9 >>> * v38.8 >>> * v39.7 >>> * v40.6 >>> * v41.6 >>> * v42.6 >>> * v43.5 >>> * v44.5 >>> * v45.4 >>> * v46.3 >>> * v47.2 >>> * v48.1 >>> * v49.1 >>> >>> It's available at the normal places: >>> >>> git://github.com/linux-rdma/rdma-core >>> https://github.com/linux-rdma/rdma-core/releases >>> >>> ---
