I like the proactive approach to EOLing branches, but I don't think we can quite EOL a branch when there is no newer branch (2.2.0) out. If that's 2.1.6, that's fine.
On Thu, May 16, 2019 at 3:18 PM Stack <st...@duboce.net> wrote: > Was going to put up an RC for 2.1.5 in next day or so after a review of > unresolved JIRAs that have 2.1.5 as fix version. It is coming up on two > months since 2.1.4 and by the time we're done, there'll be 90+ changes. > Branch-2.1 nightlies have started to stabilize again. > > Was also thinking of EOL'ing the 2.1 branch. We EOL'd 2.0 branch at 2.0.5. > We have too many branches as it is. What do folks think? 2.2.0 isn't out > yet so maybe wait on 2.1.6? That'd be fine too. > > Thanks, > S >
