[Mod-auth-devel] 0.9 Release and 1.0 Plans

[Paul Q. <ch...@fo...>]

Ive built and done simple testing of RC1 + my small changes on:
 - Lunar Linux x86 - (2.4.23)
 - Debian Unstable x86 - (2.6.4-RC1)
 - Gentoo Linux SPARC - (2.4.22)
 - FreeBSD x86 - (5.2-CURRENT)=20

I am +1 on a 0.9.0 Release from the CVS HEAD.

Once the release is rolled we need to make the release announcements.

Possible Announcement:
"The 0.9.0 Release of mod_authn_dbi adds several new SQL query keywords,
fixes a crash if the database server is down, removed native SHA1
Support (now supported via APR), fixed several possible security bugs
and changes the license to the Apache Software License 2.0.  All users
are recommended to upgrade."

Recommendations welcome :)

For 1.0 I am pondering removing all the authn_dbi database pooling
code.  I would like to move it into mod_dbi_pool.  The major problem I
see with having it in a separate module is that it increases the barrier
to entry -- it requires more work to get started. =20

One possible solution is to include mod_dbi_pool in the mod_authn_dbi
releases. This is sort of nasty once mod_dbi_pool is used by other
modules, but it would make life easier for end users.

The other option is just to ignore the 'ease of setup' factor and do
what logically makes sense: moving database pooling to another module.=20
With the pooling in another module, It would be useful for modules like
mod_vhost_dbi(on my hard drive - not released yet),
mod_ftpd_dbi_provider, and any scripting languages in apache modules
that would like to use pooled libdbi connections.

Moving database pooling out of authn_dbi would greatly simplify the
authn_dbi module, making a re-factor of the code easier.  This is the
major thing I want done before 1.0. Most of the other goals in the TODO
are Testings or Documentation related.  Is there any other major code
related changes you want before 1.0 Axel?

- Paul Querna