The draft that was here has been published at: https://github.com/scala/scala/releases/tag/v2.13.3
If you notice anything in the notes that could be improved, you can still comment on this gist and I'll see it and respond.
The draft that was here has been published at: https://github.com/scala/scala/releases/tag/v2.13.3
If you notice anything in the notes that could be improved, you can still comment on this gist and I'll see it and respond.
It's probably a sufficient fix, yes. Beyond that it's a matter of style of the release notes. It's the kind of things I spell out in release notes, but then my release notes are more section-oriented whereas the Scala release notes are more bullet-oriented, so YMMV.
@SethTisue
I recommend putting the instructions to silence those directly in the release notes. IME they cause lots of new warnings, so everyone will want those. The instructions in the PR are not self-explanatory and are written for a special audience (e.g., the
scala
incantations have--scala-pr 8833
; that's not a typical command line for users).