Issue tracker overflowing with '---' issues

[Max Bowsher <ma...@ukf.net>]

The issue tracker currently contains 167 '---' (untriaged) issues.

I'm torn between suggesting that we bulk reassign them all to
'unscheduled' and then try to keep on top of triaging new issues, or try
to gradually work through the existing ones.

What do people thing?

Max.

Re: Issue tracker overflowing with '---' issues

["C. Michael Pilato" <cm...@collab.net>]

Karl Fogel wrote:
> I think this might be time to post to users@ and organize a massively
> parallel effort to triage those things.  Come up with some basic
> criteria for people to use:
> 
>    1. Does it cause dataloss?
>    2. Does it cause working copy or repository breakage?
>    3. Anything else important we can think of?

      4. Is it a regression from a previous release?

-- 
C. Michael Pilato <cm...@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Re: Issue tracker overflowing with '---' issues

[Karl Fogel <kf...@red-bean.com>]

Max Bowsher <ma...@ukf.net> writes:
> The issue tracker currently contains 167 '---' (untriaged) issues.
>
> I'm torn between suggesting that we bulk reassign them all to
> 'unscheduled' and then try to keep on top of triaging new issues, or try
> to gradually work through the existing ones.
>
> What do people thing?

I think this might be time to post to users@ and organize a massively
parallel effort to triage those things.  Come up with some basic
criteria for people to use:

   1. Does it cause dataloss?
   2. Does it cause working copy or repository breakage?
   3. Anything else important we can think of?

If an issue doesn't meet one of those criteria, put it in 'unscheduled'.
Otherwise, leave it in '---'.  If you're in doubt, or you think it might
belong in a real milestone, go into #svn-dev and ask for opinions.

That's the basic idea.  Want to organize it?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org