Is there a road map, a release schedule, prioritised backlog
- Dominant language
- Rust
- Stars
- 14.6k
- Forks
- 734
- Avg merge
- 8h 40m
- Merged PRs (30d)
- 4
Description
While I think this is a fantastic project and wish you all the success in the world, it does look like chaos.
I arrived here because I thought this was going to be component of future release of Windows.
At the moment I don't see that happening at all.
I suggest you need
- a road map which contains what direction the project is going in.
- to know the feature set that Microsoft are expecting for the first release
- a prioritised back log of features/user stories etc
- an automated test mechanism/framework to prevent regression
- a release plan for how this will be include in the localised releases of Windows
For example the other Microsoft projects on GitHub have working groups and prioritise the features to be developed. Many feature requests are rejected.
Contributor guide
Research direction
No file, test, or entry point is named. Begin by checking whether the project has a documented roadmap, prioritised backlog, release schedule, and automated test framework, then compare those gaps with the requested Windows release and localisation planning. Done means the requested direction, priorities, testing approach, and release plan are documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100