From c75ba544b4583eb22605e30930404ed1d4456e7c Mon Sep 17 00:00:00 2001 From: Philip Zembrod Date: Fri, 19 Jul 2024 14:40:36 +0200 Subject: [PATCH] Spelling out the GitHub procedure in Release-howto.md --- Release-howto.md | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/Release-howto.md b/Release-howto.md index 5205bbc..ff61526 100644 --- a/Release-howto.md +++ b/Release-howto.md @@ -45,5 +45,16 @@ are still in the old or possibly an intermediate state, and * Review and finalize new version description in `Versions.md`. This will also become the release description on GitHub. Commit `Versions.md`. * Run `git push origin` to push changes to GitHub. -* Create release on GitHub. -* \ No newline at end of file +* Create release on GitHub: + * Use name "cc64 vX.YZ" and tag "vX.YZ" which then will be created by + GitHub. + * Copy/paste the markdown text from `Versions.md` into the GitHub + release description text. Check it in Preview, esp. check that the + links work. Relative source links don't work here; they need to be + full work https links. Also, line breaks in the markdown of the + description are rendered as line breaks in the resulting html page. + * Save the release as draft. +* Run `make release`. Open the directory `./release/` in the file manager + and drag them to the field on the GitHub release page marked by + "Attach binaries by dropping them here or selecting them." +* Publish the release.