Decide on a better strategy for release notes/changelogs
Open
Nobody has claimed this yet.
enhancement
meta
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Currently, we're generating changelogs with a Python script. This is trying to mimic the exact format that rustup posts on the Rust blog have been in the past, but it would be nice to simplify this approach.
See more discussion in https://github.com/rust-lang/rustup/pull/3773#discussion_r1576087894.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Python script that currently generates changelogs and the discussion in rustup#3773 linked from this issue. Decide on a simpler release-notes strategy and document the resulting approach; done means the project has agreement on how changelogs should be generated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- documentation, release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100