Ilja Booij wrote:

Aaron Stone wrote:

Ilja Booij <[EMAIL PROTECTED]> said:

I'd like to release 2.0rc8 (yes, flawed release engineering etc, no need to discuss that right now I think) tomorrow, August 17th (at about 4pm CET(=3pm GMT)). I'm not aware of any issues that should be resolved at the moment. am I correct? Please correct me if I'm wrong.


Sounds good! Main things in this release:

- All new command line switches
- PID files for all daemons
- Database prefixes
- Misc. bugfixes

Things still broken:

- users table and LDAP integration

So RC8 will be about making sure that the new stuff works, and RC9 will be about making sure that LDAP works. Does that sound right? Anything else to
test?
I'm wondering about the amount of work that needs to go into making LDAP authentication work. Can someone (Aaron, Paul) give an indication about it. I'll try to get up to speed on LDAP programming ASAP. Can somebody point me to some good tutorials/manuals on the web?

On the other hand... It's probably more useful to release first, and fix LDAP support later. LDAP is a big thing, and might better wait until after release. I reckon most current users won't need LDAP, and thus will be happily running DBMail 2.0 while we fix LDAP support. The only problem that I see in this respect is the fact that we might have to make a small change in the database structure, but this can be tackled by supplying good migration scripts.

Of course, nothing is preventing anyone from fixing LDAP now. We can just put it in later (and people that want to run with LDAP support can use a patch).

What do you think?

Talking of migrationscripts:
It might be wise to build some functionality into DBMail for checking the structure of the database. This function can check for the existence of tables and their fields. If this is run on every startup, we can prevent running we have faulty database. Just a thought.

Ilja



--
Ilja Booij
IC&S B.V.

Stadhouderslaan 57
3583 JD  Utrecht
www.ic-s.nl

T algemeen: 030 6355730
T direct: 030 6355739
F: 030 6355731
E: [EMAIL PROTECTED]

Reply via email to