Revive, 2022/07/21 is due. Let's release 1.7.2 and officially EOL 1.x? Thanks.
Andrew Purtell <[email protected]> 于2022年3月21日周一 13:00写道： > In your earlier response you said: > > > I'm also +1 for the last date 2022/07/21(seems adequate) > > If this is ok, then we should do one more release and it would make sense > to do the one final release at the time of EOM. For your consideration. > > > > On Mar 20, 2022, at 8:43 PM, Reid Chan <[email protected]> wrote: > > > > > >> > >> I did not claim that you ‘ran away’ > > > > I misread, pardon me :{ > > > >> Just that you did not do additional releases after 1.7.1. > > > > Yep, I knew... > > Let me schedule some time to do the 1.7.2 release > > > > > >> On Mon, Mar 21, 2022 at 11:20 AM Andrew Purtell < > [email protected]> > >> wrote: > >> > >> Greetings Reid. I did not claim that you ‘ran away’ just to be clear. > :-) > >> Pardon the informal language. Just that you did not do additional > releases > >> after 1.7.1. > >> > >> > >>>> On Mar 20, 2022, at 8:10 PM, Reid Chan <[email protected]> > wrote: > >>> > >>> Hi ah, I'm always here, still checking emails everyday, not running > >> away. > >>> > >>> Less active is just because I'm busy at work and training new > colleagues, > >>> some of them have been active in the HBase community for some time, and > >> one > >>> of them also became a committer. (kind of being active in another way > >> :D) > >>> > >>> Back to the branch-1: > >>> +1 for the voices from the user channel > >>> > >>> I already arranged my guys to work on the comparison between 1.x and > 2.x, > >>> there will be results and following-ups in the upcoming season 2 > (April - > >>> Jun) > >>> So I'm also +1 for the last date 2022/07/21 (seems adequate) if > >> everything > >>> is as scheduled > >>> > >>> > >>> ------ > >>> Best regards, > >>> R.C > >>> > >>> > >>> > >>> > >>>> On Sun, Mar 20, 2022 at 1:19 AM Andrew Purtell < > >> [email protected]> > >>>> wrote: > >>>> > >>>> Sure. It’s fine to ask. > >>>> > >>>> The issue is lack of interest and resources for releasing, primarily. > If > >>>> someone steps up to RM the code line and can produce releases on a > >> regular > >>>> basis - and we need to see it happen, not simply accept a promise - > then > >>>> EOM would be premature. > >>>> > >>>> As things stand Reid made two (1.7.0 and 1.7.1) and then went away. > >> Since > >>>> then the branch has not been maintained by a coordinating actor and > that > >>>> makes the current state unclear. Perhaps due to the lack of attention > >> it > >>>> may still be stable, but it is in need of more considered and active > >>>> maintenance. Otherwise, it should be EOMed, in my opinion. > >>>> > >>>> > >>>>>> On Mar 19, 2022, at 7:03 AM, Sean Busbey <[email protected]> wrote: > >>>>> > >>>>> I think it’d be worth checking with user@ to see if there are > >> continued > >>>>> users of branch-1 that would be interested in getting more involved > to > >>>> keep > >>>>> the branch going with eg dependency updates and security fixes should > >>>> they > >>>>> be needed. > >>>>> > >>>>> > >>>>> > >>>>>> On Fri, Mar 18, 2022 at 11:43 PM Viraj Jasani <[email protected]> > >>>> wrote: > >>>>>> > >>>>>> +1 for the EOM of branch-1. We occasionally commit few minor fixes > if > >>>>>> required, beyond that it doesn’t get much attention. > >>>>>> Perhaps no need to wait for one year anniversary of 1.7 release if > we > >>>> have > >>>>>> sufficient votes to retire branch-1 sooner? > >>>>>> > >>>>>> > >>>>>> On Fri, 18 Mar 2022 at 3:06 AM, Andrew Purtell <[email protected] > > > >>>>>> wrote: > >>>>>> > >>>>>>> We previously discussed this topic on this thread: > >>>>>>> > >>>>>>> https://lists.apache.org/thread/hlp18jjjxxpf62spd8zkhmht23hmpljg > >>>>>>> > >>>>>>> Is it time to consider EOL of branch-1 and all 1.x releases ? > >>>>>>> > >>>>>>> There doesn't seem to be much developer interest in branch-1 beyond > >>>>>>> occasional maintenance. This is understandable. Per our > compatibility > >>>>>>> guidelines, branch-1 commits must be compatible with Java 7, and > the > >>>>>> range > >>>>>>> of acceptable versions of third party dependencies is also > restricted > >>>> due > >>>>>>> to Java 7 compatibility requirements. Most developers are writing > >> code > >>>>>> with > >>>>>>> Java 8+ idioms these days. For that reason and because the branch-1 > >>>> code > >>>>>>> base is generally aged at this point, all but trivial (or lucky!) > >>>>>> backports > >>>>>>> require substantial changes in order to integrate adequately. Let > me > >>>> also > >>>>>>> observe that branch-1 artifacts are not fully compatible with Java > 11 > >>>> or > >>>>>>> later. > >>>>>>> > >>>>>>> It is my more recent observation that relatively little maintenance > >>>>>>> activity is occurring with respect to branch-1. > >>>>>>> > >>>>>>> The last release from branch-1 was 1.7.1, on 2021/07/21. > >>>>>>> > >>>>>>> If there are no more 1.x releases in the meantime, shall we use the > >>>>>>> occasion of the one year anniversary of this last 1.x release and > >>>>>> announce > >>>>>>> EOM of HBase 1.7 and all of branch-1 on or about 2022/07/21 ? > >>>>>>> > >>>>>>> -- > >>>>>>> Best regards, > >>>>>>> Andrew > >>>>>>> > >>>>>> > >>>> > >> >
