Proposal: Trace validation roadmap
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 273
- Avg merge
- 4h 12m
- Merged PRs (30d)
- 10
Description
I'd like to propose some ideas for improving our raft implementation's quality assurance using trace validation. A draft document is prepared to outline several potential improvements to achieve this.
I'd appreciate your valuable feedback and comments helping us solidify this into a solid roadmap.
You can find the proposal document in https://docs.google.com/document/d/1oaubSgCXouT6qQ5tawup49G01loBKn4tWGMokB3ejLM/edit#heading=h.c5tbkh30ka1f.
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
Start with the linked proposal document, then inspect the raft implementation's existing quality-assurance and trace-validation entry points. Done means the proposal has received feedback and become a concrete, agreed roadmap; this issue does not name files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100