[haiku-development] Re: Reviewing our use of milestones in Trac
- From: waddlesplash <waddlesplash@xxxxxxxxx>
- To: Haiku Development ML <haiku-development@xxxxxxxxxxxxx>
- Date: Thu, 22 Nov 2018 10:20:19 -0500
On Thu, Nov 22, 2018 at 6:28 AM Adrien Destugues
<pulkomandy@xxxxxxxxxxxxx> wrote:
Current status:
- Tickets get into the R1 milestone by default
No, they go into Unscheduled. This is because the R1 milestone got
especially bloated with lots of tickets and nobody was managing it. If
you are volunteering to keep it neat and tidy, well, maybe we can go
back to having it be 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
Yes, that's fine.
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).
We already do this via a time-based query, i.e. anything closed after
the milestone was shows up on the "fixes since release" page, and from
this we can build the release notes (or at least it was for the last
release...) So this manual management isn't needed, Trac already
allows us to collect what we want here.
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?
As noted above, this isn't needed.
Overall, if we actually were a "real development team" and had 2-3 of
us putting 30-40 hours a week in on Haiku, then we could use more
traditional milestone management. But as-is, I think our current setup
makes more sense.
-waddlesplash
Other related posts:
