Skip to content

Conversation

@darjutak
Copy link
Contributor

@milessabin please add a short content of what you said, I had a real hard time figuring out given the bad sound.

@milessabin
Copy link
Contributor

@darjutak looks like you got there before me. Your text is pretty much right, but it might be more clearly rendered as,

suggested that SIP proposals should include draft specification changes to save time and effort pulling the eventual spec update together.


# Minutes

Open discusion about SIP role and transition with given evolution of Scala language, from Scala 2 to Scala 3. The conversation was prompted due to the wake of Martin Odersky's keynote at Scala Days, Berlin 2018 introducing the future of Scala - Scala 3 (link to the key note will be added once published by the organisers).
Copy link
Member

@PhilippusPhilippusJun 12, 2018

Choose a reason for hiding this comment

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

typo: discussion

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Thank you, good catch!

@heathermillerheathermiller merged commit e42750f into scala:masterJun 13, 2018
Sign up for freeto 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.

5 participants

@darjutak@milessabin@sjrd@Philippus@heathermiller