spec
spec copied to clipboard
Discussion: The need for a 'backlog' milestone
The specification will have limited traffic initially. My proposal is that we have milestones for releases:
- 1.0.0-a1
- 1.0.0-a2
During the community calls, we can go through all the issues and put them in the next milestone as the community sees fit. For those that didn't make the cut, we triage them next time. This makes the 'backlog' milestone a little redundant.
Can we close this?