Hi All,

This thread discussion is a follow-up to the old thread related to
supporting JDK8 and Datanucleus 4 as the minimum version for Sentry 2.0.
This is dedicated to discuss whether we should allow using JDK8 specific
features (such as lambda functions and other useful API) in Sentry.

Advantages are that we could start using these cool features that come in
JDK8 and forget about JDK7 for all.

Disadvantages are that doing backports on older releases and/or allowing
other companies backporting fixes from Sentry 2.x will make these backports
harder because JDK7 is still in use.

Maintenance releases are not active but companies are still pretty active
on Sentry.

Questions to answer:
- What should we do?
- If we decide to keep JDK7 compatibility, how long should we keep this
until we move completely to JDK8?

In my opinion, companies will always be outdated with what we do as an
Apache community. Taking a look at what we are doing with SentryHA
redesign, this is a breaking change for companies too because fixes on this
new design may not work for other companies and/or the backports could be
harder.

However, the current Sentry 2.0 has been active with JDK7 as the support,
and users active on 2.0 may be using JDK7 environments only.

So,
Should we wait until Sentry 2.1 or newer releases to allow JDK8 features?
Should we start in Sentry 2.0?

Any thoughts?

- Sergio

Reply via email to