Known bugs and fixes
Fixed builds usually don't exist
When I find and fix a reported bug, I
check in the modified source code and report the revision number in "Fixed ver"
column in the bug report page. This might be, say, 124.
To test the fix, I build a binary, so at least one binary exists with version
6.0.124. But building and testing one binary does not mean that it is ready to
be distributed. A "real" build requires much more than this. I need to build
binaries for all supported platforms (bitness,
operating system, etc.) and update all the relevant files and scripts on my
server that handle download requests and distribution. Before doing this, I
would ideally run a full regression test on all the binaries, but this is a lot
of work and I sometimes skip that step for important bug fixes in order to make
a provisional fix available (see above). So what typically happens is that a
version that appears in the "Fixed ver" column in the bug reports is never
posted for distribution. More likely, a build with a higher version will be
posted some days after the fix.