> The number itself is meaningless as a stability indicator; Skip's > suggestion is that the number should drop with successive releases as > the unfixed bugs get more and more obscure. So 2.2.1 fixes 140 bugs, > and 2.2.2 fixes 70, and 2.2.3 fixes 15, and so on. Counting bugfixes is also meaningless because a high bug count could also indicate either someone's found a new way to identify bugs (e.g a working purify) or else there's been a period of stability which people have used to walk through and fix those old, horrible cases. Anthony
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