+1 On Mon, Mar 2, 2020 at 8:50 PM Akira Ajisaka <aajis...@apache.org> wrote:
> +1 > > -Akira > > On Tue, Mar 3, 2020 at 4:55 AM Ayush Saxena <ayush...@gmail.com> wrote: > > > +1 for marking 2.8 EOL > > > > -Ayush > > > > > On 03-Mar-2020, at 12:18 AM, Wei-Chiu Chuang <weic...@apache.org> > wrote: > > > > > > I am sorry I forgot to start a VOTE thread. > > > > > > This is the "official" vote thread to mark branch-2.8 End of Life. This > > is > > > based on the following thread and the tracking jira (HADOOP-16880 > > > <https://issues.apache.org/jira/browse/HADOOP-16880>). > > > > > > This vote will run for 7 days and conclude on March 9th (Mon) 11am PST. > > > > > > Please feel free to share your thoughts. > > > > > > Thanks, > > > Weichiu > > > > > >> On Mon, Feb 24, 2020 at 10:28 AM Wei-Chiu Chuang < > weic...@cloudera.com> > > >> wrote: > > >> > > >> Looking at the EOL policy wiki: > > >> > > > https://cwiki.apache.org/confluence/display/HADOOP/EOL+%28End-of-life%29+Release+Branches > > >> > > >> The Hadoop community can still elect to make security update for > EOL'ed > > >> releases. > > >> > > >> I think the EOL is to give more clarity to downstream applications > (such > > >> as HBase) the guidance of which Hadoop release lines are still active. > > >> Additionally, I don't think it is sustainable to maintain 6 concurrent > > >> release lines in this big project, which is why I wanted to start this > > >> discussion. > > >> > > >> Thoughts? > > >> > > >>> On Mon, Feb 24, 2020 at 10:22 AM Sunil Govindan <sun...@apache.org> > > wrote: > > >>> > > >>> Hi Wei-Chiu > > >>> > > >>> Extremely sorry for the late reply here. > > >>> Cud u pls help to add more clarity on defining what will happen for > > >>> branch-2.8 when we call EOL. > > >>> Does this mean that, no more release coming out from this branch, or > > some > > >>> more additional guidelines? > > >>> > > >>> - Sunil > > >>> > > >>> > > >>> On Mon, Feb 24, 2020 at 11:47 PM Wei-Chiu Chuang > > >>> <weic...@cloudera.com.invalid> wrote: > > >>> > > >>>> This thread has been running for 7 days and no -1. > > >>>> > > >>>> Don't think we've established a formal EOL process, but to publicize > > the > > >>>> EOL, I am going to file a jira, update the wiki and post the > > >>> announcement > > >>>> to general@ and user@ > > >>>> > > >>>> On Wed, Feb 19, 2020 at 1:40 PM Dinesh Chitlangia < > > >>> dineshc....@gmail.com> > > >>>> wrote: > > >>>> > > >>>>> Thanks Wei-Chiu for initiating this. > > >>>>> > > >>>>> +1 for 2.8 EOL. > > >>>>> > > >>>>> On Tue, Feb 18, 2020 at 10:48 PM Akira Ajisaka < > aajis...@apache.org> > > >>>>> wrote: > > >>>>> > > >>>>>> Thanks Wei-Chiu for starting the discussion, > > >>>>>> > > >>>>>> +1 for the EoL. > > >>>>>> > > >>>>>> -Akira > > >>>>>> > > >>>>>> On Tue, Feb 18, 2020 at 4:59 PM Ayush Saxena <ayush...@gmail.com> > > >>>> wrote: > > >>>>>> > > >>>>>>> Thanx Wei-Chiu for initiating this > > >>>>>>> +1 for marking 2.8 EOL > > >>>>>>> > > >>>>>>> -Ayush > > >>>>>>> > > >>>>>>>> On 17-Feb-2020, at 11:14 PM, Wei-Chiu Chuang < > > >>> weic...@apache.org> > > >>>>>> wrote: > > >>>>>>>> > > >>>>>>>> The last Hadoop 2.8.x release, 2.8.5, was GA on September 15th > > >>>> 2018. > > >>>>>>>> > > >>>>>>>> It's been 17 months since the release and the community by and > > >>>> large > > >>>>>> have > > >>>>>>>> moved up to 2.9/2.10/3.x. > > >>>>>>>> > > >>>>>>>> With Hadoop 3.3.0 over the horizon, is it time to start the EOL > > >>>>>>> discussion > > >>>>>>>> and reduce the number of active branches? > > >>>>>>> > > >>>>>>> > > >>> --------------------------------------------------------------------- > > >>>>>>> To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > > >>>>>>> For additional commands, e-mail: > > >>> common-dev-h...@hadoop.apache.org > > >>>>>>> > > >>>>>>> > > >>>>>> > > >>>>> > > >>>> > > >>> > > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org > > For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org > > > > >
