[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Issuezilla: meaning of milestone '---' vs. 'unscheduled'

From: Branko ─îibej <brane_at_xbc.nu>
Date: 2005-09-30 06:33:26 CEST

Max Bowsher wrote:

> When an issue is initially submitted, its target milestone is set to
> '---'.
> Someone then generally changes that to 'unscheduled', if no other
> milestone is appropriate.
> I believe an unspoken policy of using this '---' -> (something else)
> transition as an opportunity to do initial triage of an issue has
> emerged. I think this is a good thing, so I'm suggesting we make this
> an actual explicit policy, so everyone understands the meaning of the
> '---' milestone as "issue awaiting initial triage".
> I don't think we need explicit criteria for passing this initial check
> - we can just leave it to a committer's sense of "is there enough
> information in this issue for us to do something useful?"

How about arranging for Issuezilla to initially create issues in the
UNCONFIRMED state? Bugzilla can do that, so I expect that Issuezilla
could, too. Using a state is a lot better than using a milestone.

-- Brane

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 30 06:34:20 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.