> Another question is whether we want to publish binary releases for the
> 'old' patch releases, i.e. 2.4.0.

Since we have compat module available (2.4.0), we might want to release it
too, but on the other hand, if we don't have active jenkins tests running
on a regular basis for old patch release, it might be difficult for us to
know how stable it really is. So, perhaps dropping binary release might be
a better option for subsequent minor release (not patch) of Phoenix.


On Tue, Feb 16, 2021 at 5:48 PM Istvan Toth <[email protected]>
wrote:

> Hi!
>
> I like this solution.
>
> Another question is whether we want to publish binary releases for the
> 'old' patch releases, i.e. 2.4.0.
>
> BTW 2.2 and 2.1 doesn't support all releases, 2.2 requires HBase 2.2.5+,
> and 2.1 requires HBase 2.1.6+,
> we didn't keep the old compatibility modules during development.
>
> Istvan
>
> On Tue, Feb 16, 2021 at 1:07 PM Viraj Jasani <[email protected]> wrote:
>
> > Hi,
> >
> > While supporting a new HBase patch release version (e.g 2.4.1), if it
> turns
> > out to be incompatible with existing HBase minor release profile (e.g
> > profile 2.4), we might have to consider some extra steps.
> >
> > Proposals:
> > 1. Add a new profile for each compat module
> > 2. Profile with HBase minor version always support latest supported HBase
> > compat module and HBase patch release (e.g in our case, profile 2.4 uses
> > compat-module 2.4.1, and profile 2.4.0 uses compat module 2.4.0)
> > 3. We run jenkins tests only for latest minor release profiles (e.g with
> > profiles 2.4 and 2.4.0 in place, we run tests for profile 2.4 only, which
> > points to latest version 2.4.1)
> >
> > HBase profile to build compatibility examples:
> >
> > *Profile for HBase minor version:*
> > 2.1 (supports all 2.1.x releases),
> > 2.3 (supports all 2.3.x releases),
> > 2.4 (if we have profile 2.4.0, 2.4 profile supports 2.4.1+ releases and
> not
> > 2.4.0)
> >
> > *Profile for HBase patch version:*
> > 2.4.0 (supports only 2.4.0 release)
> >
> > Thoughts?
> >
>
>
> --
> *István Tóth* | Staff Software Engineer
> [email protected] <https://www.cloudera.com>
> [image: Cloudera] <https://www.cloudera.com/>
> [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
> Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
> on LinkedIn] <https://www.linkedin.com/company/cloudera>
> <https://www.cloudera.com/>
> ------------------------------
>

Reply via email to