it's been a week and still no branch-2.3 or timeline on 2.3.0 RCs. Duo are you still wanting to wait for EOM on branch-2.1? If you want to wait we're coming up on the time we need to start 2.1.10 RCs; can you find a RM willing to keep doing them?
On Mon, Mar 2, 2020 at 6:55 PM 张铎(Duo Zhang) <[email protected]> wrote: > IIRC the decision is to wait until we have a 2.3.x release and also the > stable pointer has been moved to 2.2.x. > > Now the stable pointer is there, but no 2.3.x release yet. > > So I propose we send out the EOL notice after we create branch-2.3? This is > a sign that 2.3.x will come out soon. > > Stack <[email protected]>于2020年3月3日 周二02:08写道： > > > Sounds good to me. > > S > > > > On Mon, Mar 2, 2020 at 6:34 AM Sean Busbey <[email protected]> wrote: > > > > > Hi folks! > > > > > > The Apache HBase 2.1.z release line started in July 2018. It has had a > > > total of 10 releases, the last of which was mid-February of this year. > > > > > > In the end of January we made 2.2.3+ our "stable" release pointer. > > > That effectively says that as a community we believe everyone on an > > > earlier release should upgrade to that as a minimum. Ideally that > > > should mean no new folks coming in will start adopting HBase 2.1. > > > > > > I think we should EOM branch-2.1. It will reduce our maintenance work > > > as a project and provide an additional indicator to downstream folks > > > that they should be running HBase 2.2. > > > > > > There are a few changes sitting in git since the last release and > > > we're about due for one. What do folks think about HBase 2.1.10 being > > > the last of the 2.1.z releases? > > > > > >
