Description
Hi!
As you may have noticed https://github.com/pingcap/raft-rs/ has begun utilizing Github's milestones to track releases, and projects to track major features.
For now in Raft I've adopted a very minimal working set of habits:
- Every milestone is a version.
- Every issue is assigned to a milestone.
- Every 'story' involving multiple issues gets a Project once there are 5-ish issues.
- Projects use a kanban style layout (like Jira).
- Where possible issues are tagged. Notably any contribution that is fitting gets a "Good First Issue" and/or "Help Wanted" tag. These tags should be removed immediately when someone declares they will work on it. (As to not duplicate work and need to close someone's PR.)
- Anything with a "Help Wanted" or "Good First Issue" is fully detailed with clear instructions and requirements for acceptance.
You can see here we have a fully documented release history with all change nodes partially as a result of this. Every PR is covered, and all changes are detailed in depth.
If you are interested in adopting this set of habits, I would be happy to help you "catch up" the library's history to this current state. I have found once in place these habits do not take much time and do not create much administrative overhead.
From a user or potential user perspective I believe that seeing good, clean project management in a library is a huge plus, and I am much more interested in both using and contributing to the crate.
I understand that some of this is currently managed inside Jira, or exists in other internal forms, but I think opening this process and allowing the community to participate can help the project grow.