scipp / scipp/copier_template

Scripts to prepare releases

Open
#35 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jinja
Stars
2
Forks
2
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the existing tox targets that check and replace RELEASE_PLACEHOLDER, then inspect the copier template and release workflow. Review how release notes contain placeholders in commented-out templates and compare the proposed split-document approach. Done means the template has usable release targets, the workflow runs the check, and the manual preparation process is documented.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, documentation, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.