scala/make-release-notes

Issues

• Generated Markdown files should have comment that describes which script generated it

  #35 opened 11 years ago by gkossakowski
  2

• updating download/index.md should be automated

  #236 opened 8 years ago by SethTisue
  0

• Resolve release date from tag on GitHub

  #36 opened 11 years ago by gkossakowski
  0

• include `api_docs:` line in scala-lang PR

  #437 opened 3 years ago by SethTisue
  0

• Automate maintenance of projects-2.xx.md

  #289 opened 6 years ago by plokhotnyuk
  3

• Separate "Available Projects" pages

  #275 opened 6 years ago by dwijnand
  1

• Catalysts on 2.13.0-M3

  #271 opened 7 years ago
  2

• scaladex for 2.13.0-M3 does not work

  #269 opened 7 years ago by Sciss
  4

• make hand-written less hand-written

  #44 opened 8 years ago by adriaanm
  1

• mention homebrew and dash?

  #135 opened 8 years ago by adriaanm
  4

• wrong entity encoding

  #43 opened 8 years ago by adriaanm
  1

• detailed text on binary compatibility should be separate from release announcement

  #151 opened 8 years ago by SethTisue
  2

• Available Projects for Scala 2.12 vs Scaladex

  #200 opened 8 years ago by MasseGuillaume
  4

• notes on possible 2.12 release notes improvements

  #202 opened 8 years ago by SethTisue
  24

• re-iterate colorful REPL

  #136 opened 9 years ago by adriaanm
  1

• Add permalink to generate release notes

  #132 opened 10 years ago by gkossakowski
  0

• Add Typesafe logging

  #60 opened 10 years ago by adriaanm
  1

• MakeReleaseNotes.genPR throws exception

  #122 opened 11 years ago by peter-empen
  1

• scalatest_2.11.0-RC3-2.1.2

  #65 opened 11 years ago by adriaanm
  0

• proper credit

  #61 opened 11 years ago by adriaanm
  0

• document SI-8358 scala-xml is on boot classpath by default

  #55 opened 11 years ago by adriaanm
  0

• note SI-4577

  #49 opened 11 years ago by adriaanm
  0