phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Istvan Toth <st...@apache.org>
Subject Re: [DISCUSS] EOL 4.16 and 4.x?
Date Wed, 19 May 2021 06:21:43 GMT
Hi!

I am looking forward to less backports, and I want to use Java 8 features
freely as much as the next developer.

However, I'm going to play the devil's advocate here, and spell out what
Ankit hinted at:

We know that SFDC is the main contributor, and probably also the single
largest user of Phoenix, and that they still use 4.x in production.
Dropping 4.x and causing SFDC to maintain their production branch
internally may not be in the best  interest of the Apache project,
as it may divert SFDC resources from the public branches, and may result in
delaying or even missing fixes there.

I think that it would be useful to know what EOL schedule would work best
for SFDC, and align our plans with that.

Perhaps Lars or someone else from SFDC could share their "official"
opinion, and help set an EOL schedule that works for everyone.

Istvan

On Tue, May 18, 2021 at 11:30 PM Ankit Singhal <ankitsinghal59@gmail.com>
wrote:

> +1 for EOL'ing 4.x branches.
>
> As Josh and I, share the feedback from the same set of users,
> it would still be a good idea to hear from others but as it's been already
> been 12 days since your first mail out, just a notice can be given for
> 72hrs(?)
> before dropping the next 4.x versions from JIRA and cleaning branches in
> case any volunteer comes up to maintain these branches.
>
>
>
>
>
> On Mon, May 10, 2021 at 9:27 PM Josh Elser <elserj@apache.org> wrote:
>
> > No objections over here! Y'all already know the work Istvan and Richard
> > have been doing to push on Phoenix 5.1. That continues to be our focus.
> >
> > On 5/7/21 11:13 AM, Viraj Jasani wrote:
> > > Hi,
> > >
> > > Based on HBase community's decision to EOL branch-1 after 1.7.0 release
> > as
> > > per the discussion thread [1], it is inevitable that we will also have
> to
> > > consider EOL of 4.x release line sometime soon.
> > >
> > > As we have discussed in the past, even though Phoenix 4.x should
> support
> > > Java 7 only (as it supports HBase 1), we are not strictly following
> this
> > > compatibility. With HBase 2 / Phoenix 5, we no longer have to worry
> about
> > > this source compatibility. Tephra also continues to support HBase 1 and
> > > hence should follow Java 7 source compatibility rules and yet I see
> many
> > > Java 8 Optional imports in tephra-hbase-compat-2.x modules. Source
> > > compatibility is just one of the reasons behind HBase community's
> > decision
> > > to EOL branch-1, many other important reasons are discussed over thread
> > [1].
> > > Overall, HBase 2 is already widely adopted and deployed in production
> and
> > > so should be Phoenix 5 IMHO.
> > >
> > > Given that there are no apparent functional differences b/ 4.16 and
> > 5.1(and
> > > master) except for maybe few pending forward-ports (if any), I believe
> it
> > > is worth considering the ongoing 4.16 patch release as the last one on
> > 4.x
> > > release line and EOL 4.16 and 4.x.
> > > Thoughts?
> > >
> > > 1. https://s.apache.org/rs2bk
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message