[DBD-SQLite] Things to do before the next production release

Adam Kennedy adamkennedybackup at gmail.com
Fri Aug 14 02:49:17 GMT 2009

Even though there's nothing critical that requires a release of
DBD::SQLite from the sqlite.org recommendation point of view, we've
now got a fair bit of extra features, so I'd like to start thinking
about the next prod release.

>From the CPAN Testers side, there's two issues we need to chase down and fix.

The first is a false unknown on some platforms with bad C compiler
setups or missing C compiler setups.


I'd like to see this detected at Makefile.PL-time and converted to a NA result.

The second is the ongoing problem with warnings in t/08_busy.t

We need to decide if this is something we should fix (and if so
someone needs to chase down the CPAN Testers and see if you can get
access to systems, or otherwise replicate the problem) or if we should
just remove the Test::NoWarnings usage in that test script and allow
the warning to stand.

Otherwise, the latest dev release looks fine and I think we're pretty
close to being ready to release (pending a code review on all the new
contributions by everyone)

Adam K

More information about the DBD-SQLite mailing list