Hi there,
I find the current use of milestones a bit unpractical and would like to
suggest some changes.
Current status:
- Tickets get into the R1 milestone by default
- Whenever something needs ABI breakage, it gets moved to R2
- When something is a "not R1" thing (eg. multiuser), it gets moved to
Unscheduled
This is all fine. However we also have milestones for alphas and beta release.
It would be very convenient if we could get a good idea of what the changes
from beta1 to beta2 are, just by looking at closed tickets in the beta2
milestone. It would also simplify extracting stats for release notes ("over xxx
tickets were fixed in this release" or the like).
As a result, I think closed tickets should be moved to the next milestone
(currently beta2) instead of staying in R1 or Unscheduled. This will give us a
better overview of our progress, I think?
--
Adrien.
