Changelog changes
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4.4k
- Forks
- 675
- Avg merge
- 22h 29m
- Merged PRs (30d)
- 1
Description
In the last release meeting (https://github.com/nodejs/Release/issues/564) we discussed altering the layout of our changelogs.
- Ideal if the author could write the notable change section, but unlikely to happen based on the usage of the notable change label.
- Suggestion to create a Google doc to collaborate on notable changes.
- Suggestion to separate out test changes, and some doc changes to make the changelog more readable for end users.
- Remove labels from individual commits that are not major or minor.
- Suggestion to add semverness to the commit message.
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 linked release meeting discussion and the proposals in this issue. Work is done when the changelog layout and related labeling or collaboration process have an agreed, documented direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100