> I think that if the primary purpose of measuring stability is > communicating it to a large user population, including managers and > decision makers. We need to have only one or two easy to understand > metrics. I don't think we need metrics. I imagine bugs fixed per month is as uninteresting as lines of code to the average PHB (pointy-haired boss), if it's not their own product. They just want us to say "this one's good". I'd be happy to give a guideline that says "all 2.x.0 releases are solid but may contain untested code and surprises; all 2.x.1 and beyond are stabilized." --Guido van Rossum (home page: http://www.python.org/~guido/)
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