we have not yet had consensus to delete old branches. you will see we still
have them going back quite a ways. please start a new DISCUSS thread if you
want to pursue it.

On Wed, May 20, 2020 at 2:39 PM Nick Dimiduk <ndimi...@apache.org> wrote:

> Can we delete the old branch as well?
>
> On Wed, May 20, 2020 at 07:57 Sean Busbey <bus...@apache.org> wrote:
>
> > I updated the header. might take a bit for it to sync up.
> >
> > On Wed, May 20, 2020 at 9:55 AM Sean Busbey <bus...@apache.org> wrote:
> >
> > > hurm. looks like we missed some steps on cleaning up branch-2.1. the
> EOL
> > > isn't listed on our header for downloads.apache.org.
> > >
> > > we sent a notice to user@hbase in March when 2.1.10 was coming out:
> > > https://s.apache.org/om9lb
> > >
> > > On Wed, May 20, 2020 at 3:28 AM ramkrishna vasudevan <
> > > ramkrishna.s.vasude...@gmail.com> wrote:
> > >
> > >> Oh my bad. I did not realize that. Thanks for letting me know.
> > >>
> > >> On Wed, May 20, 2020, 1:54 PM Peter Somogyi <psomo...@apache.org>
> > wrote:
> > >>
> > >> > The branch-2.1 reached End of Life so the builds got disabled. The
> > last
> > >> > release from branch-2.1 is 2.1.10.
> > >> >
> > >> > On Wed, May 20, 2020 at 9:48 AM ramkrishna vasudevan <
> > >> > ramkrishna.s.vasude...@gmail.com> wrote:
> > >> >
> > >> > > Hi All
> > >> > >
> > >> > > After we did some recent checkins for branch-2.1 and was waiting
> for
> > >> the
> > >> > > nightly builds observed that the builds have not been running for
> > >> last 10
> > >> > > days.
> > >> > >
> > >>
> https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/lastBuild/
> > >> > >
> > >> > > Recently there was a compilation issue caused by  HBASE-24186
> which
> > I
> > >> > > reverted couple of days ago.
> > >> > >
> > >> > > Is there a way we can trigger the nightly build once again? Or it
> is
> > >> some
> > >> > > other known issue as in branch-2.2 (where a recent discussion had
> > >> > > happened).
> > >> > >
> > >> > > Regards
> > >> > > Ram
> > >> > >
> > >> >
> > >>
> > >
> >
>


-- 
Sean

Reply via email to