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

next steps: 1.15.0 versus 1.14.2 #540

Closed
non opened this issue Sep 18, 2019 · 6 comments
Closed

next steps: 1.15.0 versus 1.14.2 #540

non opened this issue Sep 18, 2019 · 6 comments

Comments

@non
Copy link
Contributor

non commented Sep 18, 2019

First, some background:

  • The 1.14.x series will maintain source- and binary-compatibility with 1.14.0.
  • The 1.15.x series will preserve binary-compatibility with 1.14.0 but is expected to break source-compatibility (e.g. removing the implicit keyword from some definitions)
  • We are planning to drop support for Scala 2.10 in 1.15, but we kept this in for the 1.14.1 release.

Now that 1.14.1 is out, @ashawley and I were discussing next steps. My proposal is that we start merging PRs intended for 1.15.x to master. If we don't encounter major bugs in 1.14.1 I'd prefer not to have to do a 1.14.2 release and go right to 1.15.0. If we do need 1.14.2, we can create a 1.14.x branch off of the 1.14.1 tag at that time and go from there.

How does that sound? Any objections? Am I missing anything?

cc @SethTisue @ashawley et al.

@smarter
Copy link
Contributor

smarter commented Sep 19, 2019

i suggest creating a 1.14.x branch just for the record even if nothing more ends up pushed to it.

@ashawley
Copy link
Contributor

Yes, a 1.14.x branch would likely be useful. It's what's been done in the past.

@ashawley
Copy link
Contributor

I had some small changes that might be good to merge to master and include in a 1.14.x branch from there rather than the 1.14.1 tag. In the meantime, it may also be good to listen for 1.14.1 feedback for a week or so. It wouldn't need to hold up making PRs for 1.15.

@ashawley
Copy link
Contributor

FYI: In light of #557, we will have to consider a 1.14.2 release.

@ashawley ashawley modified the milestone: 1.14.2 Sep 21, 2019
@non
Copy link
Contributor Author

non commented Sep 25, 2019

1.14.2 is released -- once we've attached the release notes I'll post about it publicly.

@non non closed this as completed Sep 25, 2019
@ashawley
Copy link
Contributor

Thanks, Erik, for doing the release.

I expect in the age of Scala Steward we probably get a lot of downstream projects running a release quicker than in years previous.

smarter added a commit to dotty-staging/scalacheck that referenced this issue Jun 3, 2020
dbaeb80 broke binary compatibility by
making `BooleanOperators` private, this does not match the plan discussed
in typelevel#540:

> The 1.15.x series will preserve binary-compatibility with 1.14.0 but
  is expected to break source-compatibility (e.g. removing the implicit
  keyword from some definitions)

This commit implements that: BooleanOperators is public again but is
also made non-implicit.
@ashawley ashawley mentioned this issue Jun 4, 2020
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

No branches or pull requests

3 participants