Subject: Re: [boost] [#1497] Ruling needed on tracker usage
From: Daniel James (daniel_james_at_[hidden])
Date: 2009-05-31 13:21:41
2009/5/29 Beman Dawes <bdawes_at_[hidden]>:
> In an organization with paid developers and paid managers, it might be
> possible to look at the tickets, look at the people and other resources
> available, assign milestone priorities accordingly, and then use progress on
> clearing them as a metric to guide release activities.
> But I'm at a loss for how we could use such milestones for Boost. So any
> ideas would be appreciated if folks think the milestones do have a place in
> Boost's process of getting releases out.
Yep, automatically assigning all new tickets to the next milestone is
unrealistic. So maybe new tickets could be set to 'to be determined'
and then maintainers could update the milestone when they accept a
ticket. And then, hopefully, the only tickets with that milestone will
be ones that somebody intended to fix in that release. It might also
be worth checking show stoppers, even if it's only to demote them.
Hopefully that system wouldn't require too much effort.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk