You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Sean Busbey <bu...@apache.org> on 2022/01/21 17:57:58 UTC
[VOTE] EOL for HBase 2.3
Hi folks!
Discussion threads:
https://s.apache.org/i56se
https://s.apache.org/w1rit
tl;dr: we look to have consensus but missed formalizing things.
+1 for EOL?
Re: [VOTE] EOL for HBase 2.3
Posted by "张铎(Duo Zhang)" <pa...@gmail.com>.
+1
Andrew Purtell <ap...@apache.org>于2022年1月22日 周六03:25写道：
> +1
>
>
> On Fri, Jan 21, 2022 at 9:58 AM Sean Busbey <bu...@apache.org> wrote:
>
> > Hi folks!
> >
> > Discussion threads:
> >
> > https://s.apache.org/i56se
> > https://s.apache.org/w1rit
> >
> > tl;dr: we look to have consensus but missed formalizing things.
> >
> > +1 for EOL?
> >
>
>
> --
> Best regards,
> Andrew
>
> Unrest, ignorance distilled, nihilistic imbeciles -
> It's what we’ve earned
> Welcome, apocalypse, what’s taken you so long?
> Bring us the fitting end that we’ve been counting on
> - A23, Welcome, Apocalypse
>
Re: [VOTE] EOL for HBase 2.3
Posted by Andrew Purtell <ap...@apache.org>.
+1
On Fri, Jan 21, 2022 at 9:58 AM Sean Busbey <bu...@apache.org> wrote:
> Hi folks!
>
> Discussion threads:
>
> https://s.apache.org/i56se
> https://s.apache.org/w1rit
>
> tl;dr: we look to have consensus but missed formalizing things.
>
> +1 for EOL?
>
--
Best regards,
Andrew
Unrest, ignorance distilled, nihilistic imbeciles -
It's what we’ve earned
Welcome, apocalypse, what’s taken you so long?
Bring us the fitting end that we’ve been counting on
- A23, Welcome, Apocalypse
Re: [VOTE] EOL for HBase 2.3
Posted by Viraj Jasani <vj...@apache.org>.
+1
On Fri, 21 Jan 2022 at 11:28 PM, Sean Busbey <bu...@apache.org> wrote:
> Hi folks!
>
> Discussion threads:
>
> https://s.apache.org/i56se
> https://s.apache.org/w1rit
>
> tl;dr: we look to have consensus but missed formalizing things.
>
> +1 for EOL?
>
Re: [VOTE] EOL for HBase 2.3
Posted by Sean Busbey <bu...@apache.org>.
Here's my +1.
That's 6 in favor and no other votes. I'll file an issue to track the clean
up work
On Sat, Jan 22, 2022 at 11:25 AM Peter Somogyi <ps...@apache.org> wrote:
> +1
>
> On Sat, Jan 22, 2022 at 6:22 PM Nick Dimiduk <nd...@apache.org> wrote:
>
> > +1
> >
> > On Fri, Jan 21, 2022 at 09:58 Sean Busbey <bu...@apache.org> wrote:
> >
> > > Hi folks!
> > >
> > > Discussion threads:
> > >
> > > https://s.apache.org/i56se
> > > https://s.apache.org/w1rit
> > >
> > > tl;dr: we look to have consensus but missed formalizing things.
> > >
> > > +1 for EOL?
> > >
> >
>
Re: [VOTE] EOL for HBase 2.3
Posted by Peter Somogyi <ps...@apache.org>.
+1
On Sat, Jan 22, 2022 at 6:22 PM Nick Dimiduk <nd...@apache.org> wrote:
> +1
>
> On Fri, Jan 21, 2022 at 09:58 Sean Busbey <bu...@apache.org> wrote:
>
> > Hi folks!
> >
> > Discussion threads:
> >
> > https://s.apache.org/i56se
> > https://s.apache.org/w1rit
> >
> > tl;dr: we look to have consensus but missed formalizing things.
> >
> > +1 for EOL?
> >
>
Re: [VOTE] EOL for HBase 2.3
Posted by Nick Dimiduk <nd...@apache.org>.
+1
On Fri, Jan 21, 2022 at 09:58 Sean Busbey <bu...@apache.org> wrote:
> Hi folks!
>
> Discussion threads:
>
> https://s.apache.org/i56se
> https://s.apache.org/w1rit
>
> tl;dr: we look to have consensus but missed formalizing things.
>
> +1 for EOL?
>