Why so soon... branch-2.2 is not stable yet. branch-2.1 is the only stable branch in 2.x since branch-2.0 is already EOL’d. Best Regards Allan Yang
张铎(Duo Zhang) <palomino...@gmail.com> 于2019年5月17日周五 上午10:23写道： > The next RC for 2.2.0 will be available soon... > > Sean Busbey <bus...@apache.org> 于2019年5月17日周五 上午10:13写道： > > > Too early to EOL 2.1. > > > > Also we didn't EOL 2.0 at 2.0.5 because folks wanted a post 2.2.0 > release. > > > > On Thu, May 16, 2019, 18:26 Zach York <zyork.contribut...@gmail.com> > > wrote: > > > > > 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 > > > > > > > > > >
