3 commits

Author	SHA1	Message	Date
forgejo-release-manager	403a81bdb5	chore(release-notes): Forgejo v7.0.12 (#6255) ... https://codeberg.org/forgejo/forgejo/milestone/8832 Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/6255 Reviewed-by: 0ko <0ko@noreply.codeberg.org> Co-authored-by: forgejo-release-manager <contact-forgejo-release-manager@forgejo.org> Co-committed-by: forgejo-release-manager <contact-forgejo-release-manager@forgejo.org>	2024-12-12 18:13:38 +00:00
forgejo-release-manager	835e72b247	chore(release-notes): Forgejo v9.0.3 (#6256) ... https://codeberg.org/forgejo/forgejo/milestone/8833 Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/6256 Reviewed-by: 0ko <0ko@noreply.codeberg.org> Co-authored-by: forgejo-release-manager <contact-forgejo-release-manager@forgejo.org> Co-committed-by: forgejo-release-manager <contact-forgejo-release-manager@forgejo.org>	2024-12-12 18:13:29 +00:00
Earl Warren	8dbd2da593	chore(release-notes): keep release notes in release-notes-published ... As of Forgejo 8.0.1 the release notes were only available in the description of the corresponding milestone which is problematic for: - searching - safekeeping The release-notes-published directory is created to remedy those problems: - a copy of all those release notes from the milestones descriptions is added. - a reference is added to the RELEASE-NOTES.md file which will no longer be used. - a symbolic link to the RELEASE-NOTES.md is added for completeness. - the release process will be updated to populate release-notes-published. The RELEASE-NOTES.md file is kept where it is because it is referenced by a number of URLs. The release-notes directory would have been a better name but it is already used for in flight release notes waiting for the next release. Renaming this directory or changing it is rather involved.	2024-12-05 17:46:14 +01:00