Skip to content

Conversation

@jvican
Copy link
Member

@jvican jvican commented Sep 23, 2016

After some thought, I believe that the compiler maintainers have a
better judgement of when proposals can be merged, especially because of
the compatibility guarantees that the Scala compiler contract enforces.

In this way, I propose that the Compiler team chooses the most
appropriate version to include the accepted proposal.

After some thought, I believe that the compiler maintainers have a
better judgement of when proposals can be merged, especially because of
the compatibility guarantees that the Scala compiler contract enforces.

In this way, I propose that the Compiler team chooses the most
appropriate version to include the accepted proposal.
@jvican jvican merged commit b3ee5b3 into scala:master Sep 23, 2016
@heathermiller
Copy link
Member

When changing the wording of the SIP document, which most people have already agreed with, I think it's best not to merge until someone (me, Seth, just anyone else on the SIP committee) has reviewed your changes.

@xeno-by
Copy link
Contributor

xeno-by commented Sep 23, 2016

Hi @heathermiller! Jorge has dropped by my office today in the afternoon, and we discussed this change. I agreed that it's a good idea, but didn't put a formal LGTM before the merge. I will be more rigorous in the future.

@jvican
Copy link
Member Author

jvican commented Sep 23, 2016

I will try to be more rigorous in the future as well, @heathermiller.

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