need to deal with client attestation & other pre-final specs before publishing errata or 1.1
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
We need to deal with the pre-final specifications - currently the 1.0 errata & 1.1 both say to use client attestation draft 7 but have draft 8 in the normative references.
I think -8 has breaking changes so we shouldn't move to it in the 1.x series but we need to double check that.
There's probably other specs too.
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 comparing client attestation drafts 7 and 8, then inspect the normative references in the 1.0 errata and 1.1 specifications. Check whether draft 8 contains breaking changes and identify any other pre-final specifications that need review. Done means the affected references and the appropriate 1.x publishing decision are clearly determined.
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
- Needs clarification
- Newbie friendliness
- 30/100