WordPress / WordPress/grunt-patch-wordpress
Add documentation for releasing a new version
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 51
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Right now, it all lives in my head. That's the wrong place for it to live.
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 gathering the release procedure from the maintainer, since the issue says it is currently undocumented and held in their head. Document the complete process in the repository; done means a newcomer can follow the written steps to release a new version.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100