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

Re: 88 (+8) issues left to reach svn 1.0

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-03-25 21:49:19 CET

Have no fear... for several months now (even before solo started sending
these), Karl and I have been thinking about automating this task and
providing a good chunk of info. In particular, I'm looking for a graph for
the find/fix rate of the project -- that is the real information that we
need for forecasting.

Unfortunately, IZ doesn't provide easy ways to query the information needed
to develop a find/fix bug report. So... I'm in process on getting direct
access to the box to run some [automated] queries against the database. From
those, we'll generate a couple things:

  * a weekly summary, like what solo has been doing (thanks!)
  * a find/fix graph for the project
  * ???

The summaries will be in text, and we'll probably post the graphs and
further detail to svn.collab.net.

Look for this to start (hopefully) next week.

[ personally, I've found solo's emails to be very helpful, but also a good
  driver for *more* information... ]

Cheers,
-g

On Mon, Mar 24, 2003 at 09:09:55AM -0600, B. W. Fitzpatrick wrote:
> solo turn <soloturn99@yahoo.com> writes:
> > defec: 55 (+5)
> > enhan: 16 (+1)
> > featu: 3 (-1)
> > task : 9 (+3)
> > patch: 5 (0)
> > issues resolved/invalid in the last 14 days: 22 (-3).
> > issues resolved/invalid relevant to 1.0 in the last 14 days: 5 (0).
>
> Solo,
>
> When I was in grammar school, and I would turn in my homework for a
> math problem like long division or something, if I just put the answer
> on the page, I would get the homework returned to me with a big "SHOW
> YOUR WORK" written across the top in red pen.
>
> While it's nice that you're tracking this sort of thing, I'm beginning
> to question the utility of it unless you're willing to "show your
> work."
>
> That is, I think that this summary report would be great at the
> beginning of the email, followed by a listing of issue numbers and
> summaries under each heading. For example
>
> defec: 55 (+5)
> enhan: 16 (+1)
> featu: 3 (-1)
> task : 9 (+3)
> patch: 5 (0)
>
> Defects:
> --------
> 3883 Broken flogthorple--needs fix
> 7382 Updating causes angst under HP-UX
> 8392 Clawfoot tub causes SIGBUS
> ...
>
> Enhancements:
> ------------
> 3779 Would like ability to send mail from svn client
> 7501 Needs more salt
> ...
>
> Features:
> ---------
> ...
> (etc.)
>
>
> Is this something that you could do? I think that if your report
> included this sort of information it would be invaluable--not only as
> a numerical metric, but seeing the issue numbers and summaries posted
> to the list every week is likely to spur developers on the list to
> be more likely pick issues off and work on them.
>
> -Fitz
>
> --
> Brian W. Fitzpatrick <fitz_at_red-bean.com> http://www.red-bean.com/fitz/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 25 21:46:49 2003

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.