check on pre-final specs before publishing 1.1 or 1.0 errata
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
We need to check on the pre-final specifications before publishing 1.1 or 1.0 errata. Some may have non-breaking changes and we can take the latest versions (and update the pre-final specs section to use the latest versions), others may have breaking changes and we need to pin the currently referenced version in the normative references.
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 inventorying the pre-final specifications referenced by the 1.1 and 1.0 errata, then compare each with its latest version. Update the pre-final specs section for non-breaking changes and pin the currently referenced version for breaking changes; done when every referenced specification has been classified and its normative reference is consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100