[DBD-SQLite] DBD::SQLite release schedule

[Adam Kennedy]

I apologise for the quick release tempo. I had hoped that by going
initially as fast as possible, we could limit the pain to one brief
amount of time and then be able to move on to the fantastic stable
future.

1.25 contains the amalgamation changes, which is the last major change
left to get us to near what I'd consider "steady state".

I pushed it to prod earlier than I'd expected, because it passed the
entire test suite pretty much effortlessly on all my machines and none
of the CPAN Testers machines reported any problems for the dev
releases.

I would consider 1.25 as the first long term release. Apart from
reorganising the way we do warnings (or god forbid, starting on more
features), there's nothing significant left to do now, and we've fixed
all existing FAIL causes that I can find.

So this is the first release that might be able to maintain a 100% PASS rate.

I'd recommend you treat 1.25 as the first release that might live for
a reasonable length of time, so it should be a good candidate for your
testing.

Anything you can find that doesn't work from here on can be considered
an interesting bug, and if you need commit to fix anything let me
know.

Adam K

2009/4/24 Toby Corkindale <toby.corkindale at strategicdata.com.au>:
> Hi,
> A brief comment about the DBD::SQLite release schedule, if I may?
> Which so far has been:
> 1.20 - 7 Apr
> 1.21 - 9 Apr
> 1.23 - 19 Apr
> 1.25 - 23 Apr
>
> We are using DBD::SQLite in some commercial applications to do some quite
> heavy lifting, are aware of various problems with the older versions, and
> would love to move to the newer, improved versions..
> However by the time I am halfway through testing a new release of
> DBD::SQLite, another version has come out, and at that point I may as well
> restart the testing all over.
>
> Maybe there should be more developer releases and less production releases?
> Or maybe not - it's hard to tell from here.
>
> I suppose what I'd like to know is - what is the roadmap?
> I'm on this mailing list, yet there doesn't seem to be any discussion about
> where its going at all. If you have ten minutes a week to keep me (and
> presumably others) up to date, we would appreciate it and find it helpful.
>
> I intended to get more involved with the coding in the new version of
> dbd-sqlite, but it seems you're all powering ahead far faster than I can
> keep up :)
>
> For the record, 1.23 looks fairly good, although there's still a couple of
> cases where it breaks down with the generic SQLITE_MISUSE error that I'll
> report once I can make it happen consistently. (But this isn't a regression
> - older versions were no better.)
>
>
> Thanks!
> Toby
>
> _______________________________________________
> DBD-SQLite mailing list
> DBD-SQLite at lists.scsys.co.uk
> http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite
>