Skip to content

Commit c75ba54

Browse files
committed
Spelling out the GitHub procedure in Release-howto.md
1 parent 725f29d commit c75ba54

File tree

1 file changed

+13
-2
lines changed

1 file changed

+13
-2
lines changed

Release-howto.md

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,5 +45,16 @@ are still in the old or possibly an intermediate state, and
4545
* Review and finalize new version description in `Versions.md`. This will also
4646
become the release description on GitHub. Commit `Versions.md`.
4747
* Run `git push origin` to push changes to GitHub.
48-
* Create release on GitHub.
49-
*
48+
* Create release on GitHub:
49+
* Use name "cc64 vX.YZ" and tag "vX.YZ" which then will be created by
50+
GitHub.
51+
* Copy/paste the markdown text from `Versions.md` into the GitHub
52+
release description text. Check it in Preview, esp. check that the
53+
links work. Relative source links don't work here; they need to be
54+
full work https links. Also, line breaks in the markdown of the
55+
description are rendered as line breaks in the resulting html page.
56+
* Save the release as draft.
57+
* Run `make release`. Open the directory `./release/` in the file manager
58+
and drag them to the field on the GitHub release page marked by
59+
"Attach binaries by dropping them here or selecting them."
60+
* Publish the release.

0 commit comments

Comments
 (0)