You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by Chinmay Kulkarni <ch...@gmail.com> on 2019/07/08 18:56:51 UTC
Volunteering to be RM for 4.15.0/5.1.0
Hi everyone,
I would like to be RM for 4.15.0/5.1.0. There are about 18
<https://issues.apache.org/jira/issues/?jql=project%20%3D%20PHOENIX%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%204.15.0>
open issues for 4.15.0 and 22
<https://issues.apache.org/jira/browse/PHOENIX-5386?jql=project%20%3D%20PHOENIX%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%205.1.0>
for 5.1.0. Thanks a lot to Lars for doing the work required for getting a
stable and quicker-running test suite and for getting the release efforts
started!
I'm working on some blockers and will be moving any new feature requests
against 4.15/5.1 to 4.15.1 and 5.1.1 respectively.
As per discussions on a previous email thread, let's aim to release a
SNAPSHOT for people to test with and ensure that the test suite keeps
passing without significant performance degradation.
Thanks,
Chinmay
--
Chinmay Kulkarni
Re: Volunteering to be RM for 4.15.0/5.1.0
Posted by Chinmay Kulkarni <ch...@gmail.com>.
Hi Artem,
The 4.15.0 release will be done for HBase-1.3, 1.4 and 1.5.
Thanks,
Chinmay
On Wed, Aug 7, 2019 at 2:35 PM Artem Ervits <ar...@gmail.com> wrote:
> Can we target 4.15 for HBase 1.5 branch to have at least one branch
> compatible with the incoming 1.x HBase release? HBase 1.3 and 1.4 are being
> discussed for EOL and also depends on an EOL version of Hadoop (2.7) so
> HBase 1.5 seems to be the bridge release.
>
> On Thu, Jul 18, 2019, 2:40 PM larsh@apache.org <la...@apache.org> wrote:
>
> > +1
> >
> > On Monday, July 8, 2019, 12:57:27 PM HST, Thomas D'Silva <
> > tdsilva@salesforce.com.INVALID> wrote:
> >
> > I don't think we need to call 4.15/5.1 an alpha or beta release. Lets
> just
> > follow our usual process and release 4.15 and 5.1,
> > (after ensuring all the ITs pass and any manual testing that needs to be
> > done). If we need to fix bugs we can have a patch release.
> >
> >
> > On Mon, Jul 8, 2019 at 11:57 AM Chinmay Kulkarni <
> > chinmayskulkarni@gmail.com>
> > wrote:
> >
> > > Hi everyone,
> > >
> > > I would like to be RM for 4.15.0/5.1.0. There are about 18
> > > <
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20PHOENIX%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%204.15.0
> > > >
> > > open issues for 4.15.0 and 22
> > > <
> > >
> >
> https://issues.apache.org/jira/browse/PHOENIX-5386?jql=project%20%3D%20PHOENIX%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%205.1.0
> > > >
> > > for 5.1.0. Thanks a lot to Lars for doing the work required for
> getting a
> > > stable and quicker-running test suite and for getting the release
> efforts
> > > started!
> > >
> > > I'm working on some blockers and will be moving any new feature
> requests
> > > against 4.15/5.1 to 4.15.1 and 5.1.1 respectively.
> > >
> > > As per discussions on a previous email thread, let's aim to release a
> > > SNAPSHOT for people to test with and ensure that the test suite keeps
> > > passing without significant performance degradation.
> > >
> > > Thanks,
> > > Chinmay
> > > --
> > > Chinmay Kulkarni
> > >
> >
>
--
Chinmay Kulkarni
Re: Volunteering to be RM for 4.15.0/5.1.0
Posted by Artem Ervits <ar...@gmail.com>.
Can we target 4.15 for HBase 1.5 branch to have at least one branch
compatible with the incoming 1.x HBase release? HBase 1.3 and 1.4 are being
discussed for EOL and also depends on an EOL version of Hadoop (2.7) so
HBase 1.5 seems to be the bridge release.
On Thu, Jul 18, 2019, 2:40 PM larsh@apache.org <la...@apache.org> wrote:
> +1
>
> On Monday, July 8, 2019, 12:57:27 PM HST, Thomas D'Silva <
> tdsilva@salesforce.com.INVALID> wrote:
>
> I don't think we need to call 4.15/5.1 an alpha or beta release. Lets just
> follow our usual process and release 4.15 and 5.1,
> (after ensuring all the ITs pass and any manual testing that needs to be
> done). If we need to fix bugs we can have a patch release.
>
>
> On Mon, Jul 8, 2019 at 11:57 AM Chinmay Kulkarni <
> chinmayskulkarni@gmail.com>
> wrote:
>
> > Hi everyone,
> >
> > I would like to be RM for 4.15.0/5.1.0. There are about 18
> > <
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20PHOENIX%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%204.15.0
> > >
> > open issues for 4.15.0 and 22
> > <
> >
> https://issues.apache.org/jira/browse/PHOENIX-5386?jql=project%20%3D%20PHOENIX%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%205.1.0
> > >
> > for 5.1.0. Thanks a lot to Lars for doing the work required for getting a
> > stable and quicker-running test suite and for getting the release efforts
> > started!
> >
> > I'm working on some blockers and will be moving any new feature requests
> > against 4.15/5.1 to 4.15.1 and 5.1.1 respectively.
> >
> > As per discussions on a previous email thread, let's aim to release a
> > SNAPSHOT for people to test with and ensure that the test suite keeps
> > passing without significant performance degradation.
> >
> > Thanks,
> > Chinmay
> > --
> > Chinmay Kulkarni
> >
>
Re: Volunteering to be RM for 4.15.0/5.1.0
Posted by "larsh@apache.org" <la...@apache.org>.
+1
On Monday, July 8, 2019, 12:57:27 PM HST, Thomas D'Silva <td...@salesforce.com.INVALID> wrote:
I don't think we need to call 4.15/5.1 an alpha or beta release. Lets just
follow our usual process and release 4.15 and 5.1,
(after ensuring all the ITs pass and any manual testing that needs to be
done). If we need to fix bugs we can have a patch release.
On Mon, Jul 8, 2019 at 11:57 AM Chinmay Kulkarni <ch...@gmail.com>
wrote:
> Hi everyone,
>
> I would like to be RM for 4.15.0/5.1.0. There are about 18
> <
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20PHOENIX%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%204.15.0
> >
> open issues for 4.15.0 and 22
> <
> https://issues.apache.org/jira/browse/PHOENIX-5386?jql=project%20%3D%20PHOENIX%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%205.1.0
> >
> for 5.1.0. Thanks a lot to Lars for doing the work required for getting a
> stable and quicker-running test suite and for getting the release efforts
> started!
>
> I'm working on some blockers and will be moving any new feature requests
> against 4.15/5.1 to 4.15.1 and 5.1.1 respectively.
>
> As per discussions on a previous email thread, let's aim to release a
> SNAPSHOT for people to test with and ensure that the test suite keeps
> passing without significant performance degradation.
>
> Thanks,
> Chinmay
> --
> Chinmay Kulkarni
>
Re: Volunteering to be RM for 4.15.0/5.1.0
Posted by Thomas D'Silva <td...@salesforce.com.INVALID>.
I don't think we need to call 4.15/5.1 an alpha or beta release. Lets just
follow our usual process and release 4.15 and 5.1,
(after ensuring all the ITs pass and any manual testing that needs to be
done). If we need to fix bugs we can have a patch release.
On Mon, Jul 8, 2019 at 11:57 AM Chinmay Kulkarni <ch...@gmail.com>
wrote:
> Hi everyone,
>
> I would like to be RM for 4.15.0/5.1.0. There are about 18
> <
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20PHOENIX%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%204.15.0
> >
> open issues for 4.15.0 and 22
> <
> https://issues.apache.org/jira/browse/PHOENIX-5386?jql=project%20%3D%20PHOENIX%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%205.1.0
> >
> for 5.1.0. Thanks a lot to Lars for doing the work required for getting a
> stable and quicker-running test suite and for getting the release efforts
> started!
>
> I'm working on some blockers and will be moving any new feature requests
> against 4.15/5.1 to 4.15.1 and 5.1.1 respectively.
>
> As per discussions on a previous email thread, let's aim to release a
> SNAPSHOT for people to test with and ensure that the test suite keeps
> passing without significant performance degradation.
>
> Thanks,
> Chinmay
> --
> Chinmay Kulkarni
>