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

roll an 0.3.0 release #180

Closed
SethTisue opened this issue Feb 7, 2019 · 10 comments
Closed

roll an 0.3.0 release #180

SethTisue opened this issue Feb 7, 2019 · 10 comments
Assignees

Comments

@SethTisue
Copy link
Member

needed over at scala/community-build#849

@SethTisue SethTisue self-assigned this Feb 7, 2019
@SethTisue
Copy link
Member Author

@SethTisue
Copy link
Member Author

@SethTisue
Copy link
Member Author

the new JDK 11 jobs failed but that's fine, we want to publish from 8. e71dc97 should fix it for next time

@SethTisue
Copy link
Member Author

SethTisue commented Feb 8, 2019

the 6 staging repos on oss.sonatype.org are orgscala-lang-1664 through orgscala-lang-1669. I hit "close" and "release" on them

@SethTisue
Copy link
Member Author

SethTisue commented Feb 8, 2019

gah, 2.11 artifacts aren't on Maven Central: https://repo1.maven.org/maven2/org/scala-lang/modules/scala-collection-compat_2.11/0.2.2/

@SethTisue SethTisue reopened this Feb 8, 2019
@SethTisue
Copy link
Member Author

haha well no wonder, wtf

  exclude:
    # ?                                                                                                                
    - jdk: oraclejdk8
      scala: 2.11.12

@SethTisue SethTisue changed the title roll an 0.2.2 release roll an 0.3.0 release Feb 8, 2019
@SethTisue
Copy link
Member Author

SethTisue commented Feb 8, 2019

I'm rolling 0.3.0. no code changes, but I want to verify that the full cross-publish goes smoothly, and @julienrf pointed out that although we aren't guaranteeing bincompat yet (that's #162), 0.2.2 wasn't bincompat with 0.2.1. seems better to bump the version number to 0.3.0 to give more indication that bincompat broke.

@SethTisue

This comment has been minimized.

@SethTisue
Copy link
Member Author

SethTisue commented Feb 8, 2019

gah, what a mess. I fixed the JDK 11 jobs to be green, green is good, but those jobs are also uploading artifacts to the staging repos, which we don't want. 😖

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

1 participant