-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kristoffer Danielsson wrote: > When can we expect a bug fix? Days, weeks, months?
Go to http://www.sqlite.org/src/reportlist and you can see all open tickets. (Currently there is no report in priority order). SQLite consortium members and paying customers get first priority. You can see the timeline for what work is being done: http://www.sqlite.org/src/timeline Other than that (and I do not speak for the SQLite team here - just a long time observer) criteria such as how many people are affected, the severity, the difficulty of the fix, the likelihood of the fix breaking something else etc are used. For example if this bug has been present in SQLite since 3.0 (5 years ago) then many people don't hit it. If you can narrow it down to the release (or even better checkin) that caused the problem then that makes it considerably easier to fix. You can do a bisection search to find the culprit. (Sadly it doesn't appear that fossil can do bisection so you'll have to do it manually.) Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrcu6IACgkQmOOfHg372QSYHQCfbQ6XSVCvbJXn3eR2u9L5WHuq +wwAoIQuky96CdIQypBHBMkhpSX9wWkz =dxic -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
