Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Scala Native to 0.4.10 and drop Scala 2.11 support #584

Closed
wants to merge 1 commit into from

Conversation

ekrich
Copy link
Contributor

@ekrich ekrich commented Mar 13, 2023

As mentioned in #579, a minor version bump on release would be great.

@ekrich ekrich closed this Mar 13, 2023
@ekrich ekrich reopened this Mar 14, 2023
@ekrich
Copy link
Contributor Author

ekrich commented Mar 14, 2023

Reopened in case people have a change of heart and want to move on.

@SethTisue
Copy link
Member

SethTisue commented Mar 24, 2023

I think in order to produce a change of heart, you need to make a case that there are a concrete benefits for Scala Native users and we're not just mechanically taking the upgrade.

(As before, I lean towards your position, but I'm not the decider, we need some degree of consensus, particularly in this repo where compatibility is paramount.)

@SethTisue SethTisue closed this Mar 24, 2023
@ekrich
Copy link
Contributor Author

ekrich commented Mar 24, 2023

Ok, no worries. I believe we should drop 2.11 for JVM for newer versions of this library. If people are upgrading and need this library for compatibility to afford the upgrade then they can use any version prior to the drop. Now that Scala Native and Scala.js have dropped support I think this is a good case. Besides, upgrading to 2.12 from normal non cross projects is just a stepping stone to 2.13 and eventually 3.0. Maintaining backward compat is nice to have for people upgrading Scala.js but doesn't help as much for Scala Native and then we have no regression tests with this library as part of the build and verification.

@ekrich ekrich deleted the topic/native0410 branch June 23, 2023 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants