Closed MarkStega closed 5 years ago
Do you mean something like this https://github.com/aspnet/AspNetCore/issues/8177 ?
Yes, that would be perfect; It doesn't have to have fixed dates or anything; just needs to give a general sense of where the project is headed and where outside contribution would be welcomed. Another example using the issue list is https://github.com/Blazored/Gitter/issues
Well I'm already using issues list as roadmap, kinda. Now I could create a special Roadmap issue and group all of the issues by release numbers.
I think the idea of having one issue that refers to the other feature/bug requests a really good idea. Even if it was a really simple vNext with these n issue references and vBacklog with the other m issue references it would be useful.
Since I'm already using milestones for each of release than this special roadmap issue would just group all of that in one place. Then I could just pin the issue so that it's always visible.
Created #88
It would be useful to have a roadmap of proposed component additions and enhancements either as an addition to the readme, and additional file, or individual issues.
As examples I'd love to know if a templated listbox or a datetime control is/are in the plans.