nervosnetwork / nervosnetwork/rfcs
When release a new edition of CKB, a tag should be created.
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 271
- Forks
- 158
- PR merge metrics
- No merged PRs in 30d
Description
Description
I think it will be good for writing documentations, especially when compare the differences of different editions.
Tags are more readable than git commit IDs, in documentations.
Today is 2024-03-18, but last tag of CKB RFCs is v2020.01.15.
Contributor guide
No contributing guide indexed for this repository
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
Review the existing CKB RFC tag v2020.01.15 and the repository's current edition or release process. Define where new edition tags should be created and document the convention; done means documentation can refer to readable tags instead of commit IDs for each edition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- documentation, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100