Skip to content

After first release/publish, set up MiMa to enforce bincompat #23

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.

Sign up for GitHub

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

Jump to bottom
Closed
SethTisue opened this issue Jul 3, 2019 · 4 comments
Closed

After first release/publish, set up MiMa to enforce bincompat #23

SethTisue opened this issue Jul 3, 2019 · 4 comments
Assignees
@SethTisue

Comments

@SethTisue
Copy link
Member

backwards-only is fine, and I think we could give ourselves permission to be liberal about bumping the version number as needed, in order not to be too saddled by this
@SethTisue
Copy link
Member Author

waiting on #20 for now

@SethTisue SethTisue self-assigned this Jul 18, 2019
SethTisue added a commit to SethTisue/scala-collection-contrib that referenced this issue Jul 19, 2019
@SethTisue
enable mima
dd5a6c8 
fixes scala#23
@SethTisue
Copy link
Member Author

fixed in #33

@lrytz lrytz closed this as completed in ff8f558 Jul 19, 2019
@joshlemer
Copy link
Contributor

joshlemer commented Jul 19, 2019 •
edited
Loading

Could we wait to pin Mima / backwards compatibility until after #24 ?

@SethTisue
Copy link
Member Author

I'm fine with considering the MiMa results just informational for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SethTisue SethTisue

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SethTisue @joshlemer