Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scripts to prepare releases #35

Open
jl-wynen opened this issue Oct 9, 2023 · 2 comments
Open

Scripts to prepare releases #35

jl-wynen opened this issue Oct 9, 2023 · 2 comments

Comments

@jl-wynen
Copy link
Member

jl-wynen commented Oct 9, 2023

Version placeholders

Due to CalVer, we need to use placeholders with versionadded and friends. In Scipp, we have tox targets to check for and replace RELEASE_PLACEHOLDER. But this does not work with the release notes which also contain a placeholder in the commented-out template that we don't want to replace.

  • Find a way around the release-note template problem (see also below).
  • Add tox targets to copier template.
  • Use the check target in the release workflow
  • Document how to use the prepare release target. (Shouldn't be done automatically because a human should check if it made a mess.)

Release notes

We need to manually remove empty sections in the release notes. I looked into writing a script to do that. But while docutils has a parser for rst, it doesn't have a writer. And similarly, if we switched to markdown files, myst-parser has a parser but also no writer. We could use a generic markdown parser but that might struggle with myst-extensions. Or we use a custom parser which could be complicated. Esp. for rst; markdown should be simpler.

Maybe splitting the release notes into separate documents, one per version, would simplify this. WE discussed this before but never implemented it.

@SimonHeybrock
Copy link
Member

We are currently not writing release notes for any of the projects using copier_template, and have instead been relying on those on GitHub. Are you suggesting this should change?

@jl-wynen
Copy link
Member Author

I don't remember what the precise reason for this was. But using release notes in the docs would still require extra work even with what I proposed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants