Skip to content

update readme for library name change #328

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

Closed
wants to merge 1 commit into from
Closed

update readme for library name change #328

wants to merge 1 commit into from

Conversation

SethTisue
Copy link
Member

@SethTisue SethTisue commented Apr 30, 2020

references #317

not for merge until we've actually published under the new name

notes to self:

  • update the Scala community build, too
  • re-enable MiMa
  • update the Scala 2.13.0 release notes
  • tweet about it from scala_lang (or even do a blog post?)

@lrytz
Copy link
Member

lrytz commented Apr 30, 2020

until we've actually published under the new name

Let's discuss this first: #331

Copy link
Contributor

@NthPortal NthPortal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there was a bunch of cleanup/consolidation that we wanted to do for the 3.0.0 release (see #292 and #288 (comment)), so we should hold off on publishing until we do that restructuring/cleanup

@julienrf
Copy link
Contributor

julienrf commented Jun 2, 2020

According to #331 should we revert #327? In all cases, if we agree on not breaking binary compatibility we should re-enable MiMa and do the check against scala-collection-compat:2.1.6.

@SethTisue
Copy link
Member Author

Lukas is pondering how to proceed here.

@NthPortal
Copy link
Contributor

it seems to me like this is PR is obsolete given the conclusion to #331. thanks though Seth 💜

@NthPortal NthPortal closed this Aug 18, 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

Successfully merging this pull request may close these issues.

4 participants