A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-April/023026.html below:

[Python-Dev] Re: Stability and change

[Python-Dev] Re: Stability and change [Python-Dev] Re: Stability and changeJeremy Hylton jeremy@zope.com
Wed, 10 Apr 2002 19:56:53 -0400
>>>>> "GN" == Gustavo Niemeyer <niemeyer@conectiva.com> writes:

  GN> Hi Jeremy!  [...]
  >> BTW, what measurements are you proposing to make?  How will you
  >> make them?  What will they tell us?

  GN> You may want to have a look at the following URL:

  GN> http://snapshot.conectiva.com.br

  GN> This was made for the exact purpose of what is being discussed.

I see lots of colors, tiny graphs, and bunches of numbers.  Example:
There are 15 normal bugs with a weight of 38.668 and an impact of
3.7.  Is that supposed to mean something? <wink>

>From this page, I can't tell how bugs are measured, how they are
classified, and what all the numbers mean.  Was all this done by hand?
It looks a little over-engineered to me.

I was imagining the answer would be something more like: Count number
of bugs marked as "closed" and "fixed" over some time interval.

Jeremy





RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4