Skip to content
This repository has been archived by the owner on May 23, 2023. It is now read-only.

How long will we maintain JDK 1.6 compatibility? #218

Open
yurishkuro opened this issue Nov 14, 2017 · 3 comments
Open

How long will we maintain JDK 1.6 compatibility? #218

yurishkuro opened this issue Nov 14, 2017 · 3 comments
Labels

Comments

@yurishkuro
Copy link
Member

No description provided.

@tedsuo
Copy link
Member

tedsuo commented Nov 15, 2017

I would want to see us sit at a stable v1 before considering a 1.8+ API. In that sense, we maintain 1.6 compatibility "forever."

@jpkrohling
Copy link
Contributor

I think we should really, really consider 1.8 as the baseline. As API providers, it would help us a lot to be able to have default implementations on interfaces. For instance, #282 would be a non-breaking change with a code like this on the SpanContext interface:

    default <T extends SpanContext> T unwrap() {
        return (T) this;
    }

@carlosalberto
Copy link
Collaborator

This issue came up during #326 and I would like to re-take this discussion on the reasons behind it (to decide the timeline to move to 1.7/1.8).

As a start, this old issue could throw light into the historical context: #75

To me, it sounds like the important bit here is to dig into any framework or service that would really need to keep support for 1.6 (at least for the near future).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants