Traditionally the release notes have been part of the paradox docs as well, there are also github release notes (not saying that we should use them but its another option considering that now Scala OS users frequently use those release notes).
Maybe we should discuss how we should move forward on this? To me I think putting the release notes in the wiki while releasing and then copying the section to github release notes when a tag is made makes sense? On Wed, Mar 6, 2024 at 10:44 PM PJ Fanning <fannin...@apache.org> wrote: > I did a quick run through the commits and put some of the main changes in > wiki > > > https://github.com/apache/incubator-pekko/wiki/Apache-Pekko-1.1.0%E2%80%90M1 > > I'll do another pass or 2 but if anyone wants to add more details - > feel free to edit the page. > > When it is ready, I can do a PR to add to the Paradox docs. > > I want to change the release notes page so that each release has its > own page and the main release note page is just a Table of Contents > linking the per-release pages. Any objections to this or alternative > proposals? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > For additional commands, e-mail: dev-h...@pekko.apache.org > > -- Matthew de Detrich *Aiven Deutschland GmbH* Immanuelkirchstraße 26, 10405 Berlin Alexanderufer 3-7, 10117 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen *m:* +491603708037 *w:* aiven.io *e:* matthew.dedetr...@aiven.io
