Skip to content

Conversation

@ashawley
Copy link
Member

@ashawley ashawley commented Apr 28, 2016

I mentioned doing this before release version 1.0.6 in #97.

I assume this is the right thing to do, but I wouldn't know if this has any unintended side effects.

@SethTisue
Copy link
Member

the latest is 2.12.0-M4

@ashawley ashawley force-pushed the crossScalaVersions-2.11.8-2.12.0-M3 branch from cdf5898 to f7ff586 Compare April 29, 2016 02:29
@ashawley
Copy link
Member Author

I amended the commit. Thank you, @SethTisue!

@ashawley ashawley changed the title Update crossScalaVersions to 2.11.8 and 2.12.0-M3 Update crossScalaVersions to 2.11.8 and 2.12.0-M4 Jun 13, 2016
@ashawley ashawley force-pushed the crossScalaVersions-2.11.8-2.12.0-M3 branch from f7ff586 to b7563ae Compare June 14, 2016 01:10
@ashawley ashawley force-pushed the crossScalaVersions-2.11.8-2.12.0-M3 branch from b7563ae to fc354d5 Compare July 12, 2016 17:58
@ashawley ashawley changed the title Update crossScalaVersions to 2.11.8 and 2.12.0-M4 Update crossScalaVersions to 2.11.8 and 2.12.0-M5 Jul 12, 2016
@biswanaths biswanaths merged commit fc354d5 into scala:master Sep 14, 2016
@biswanaths
Copy link
Contributor

Thanks again Aaron. Only if for each of thank was a dollar, Aaron would be a millionaire.

@ashawley ashawley deleted the crossScalaVersions-2.11.8-2.12.0-M3 branch September 14, 2016 17:52
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.

3 participants