On 12/2/05, Ted Husted <[EMAIL PROTECTED]> wrote: > > On 12/1/05, Don Brown <[EMAIL PROTECTED]> wrote: > > Step 2: > > - Move closed tickets included in soon-to-be-released projects to > their > > milestone. > > - Wade through TBD tickets and assign to milestones > > > > While I like Martin's idea of only putting tickets to milestones when > someone > > commits to resolving them, I'm afraid it would distort the roadmap by > giving the > > wrong impression that we are always close to a release. Perhaps we > could start > > using the "Assigned" field more often to mark which ones have been taken > up and > > which are just hanging. > > I'd be more concerned about giving people the wrong impression that > someone is going to resolve the ticket before the next release. > > IMHO, if a committer assigns a ticket to a milestone, then that > committer is saying he or she is going to make it so. > > :) Otherwise, we have a situation where someone who is not planning to > do the work is making the decision :)
Exactly. That was the reasoning behind suggesting this. We've been in this situation before (and are probably still in it!) where we've written down a roadmap, and assigned features to specific dot releases. What's actually happened, not surprisingly, is that what got done was what people wanted to work on, not what we originally thought were good plans for a roadmap. And, if the bugs are resolved, we *should* always be close to a > release. In 1.0 to 1.1 era, we were always saying "let's get this one > last feature in before we release". I don't think that worked well for > us. Gosh, that sounds just like my day job. ;-) If we start setting tickets to milestones when there is not a > volunteer ready, willing, and able to work on the ticket, we're > falling back into the old pattern that says a release has to be big to > be worthwhile. Or that the milestone attached to an issue doesn't really mean anything... Hey, I'd be in favor of releasing after any ticket is resolved. Fix a > bug, add a feature, roll a release -- works for me! It might work for me if the release process was completely automated and foolproof, but I think we're still a long way from that. ;-) -- Martin Cooper If we end up with milestones like 2.3.52, then so be it. MySQL does > that, and I never blinked. > > -Ted. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
