Avner Levy wrote: > Every time a new version of sqlite is released I need to go over all the bugs > that were fixed to that release and decide if there is a good reason to move > up to the new version. Is there a easy way for getting the list of all bugs > fixed to 2.8.13 (for example) ? I've looked in the report section and didn't > find such report. >
Not every bug fix has a ticket. Sometimes I find and fix bugs serendipitously while working on other things. Sometimes people report bugs on the mailing list without filing a ticket.
On the other hand, not ever ticket is a bug. A lot of tickets are for enhancement requests or errors in documentation. Many tickets that claim to be bugs in SQLite are really errors in the code that calls SQLite. Some people write tickets containing questions about how to use SQLite.
So you cannot really rely on tickets alone to see what has happened between two releases of SQLite. The tickets are very helpful, but you also need to look at the check-ins.
The best way to see what has changed between any two releases of SQLite is to study the timeline.
http://www.sqlite.org/cvstrac/timeline
The default timeline current provides 30 days of look-back. This is sufficient for viewing the difference between 2.8.12 and 2.8.13 (assuming you look today). For other situations, you can adjust the amount of look-back and how much detail is shown in the timeline, using parameters found at the very bottom of the timeline page. -- D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
