On Mon 09 Jan 2006 13:22, Nicolas Baradakis wrote:
Alan DeKok wrote:
I was planning on releasing it Monday, but now Tuesday or Wednesday is looking better for me.
Comments?
Sounds good to me. The pre-release has been available for 3 weeks, so I think any major problem would have been reported already.
Also, here's a list of what could be in later releases
1.1.1 - libeap fixes - netsnmp fixes
If you look at CVS log reports, I've been playing with rlm_eap makefiles recently, and manage somehow to fix the esoteric libtool warnings for libeap. Now CVS head is building fine without RLM_EAP_LINK_MODE=-static. It'd be nice if other people can test these changes, though.
For 1.1.1 we could also make a sweep over all the modules to back-port more fixes to be found in CVS head. We could also make a sweep over the bugzilla, too.
And finally, if someone has a setup with ldap backend, and is volunteering to test the patch under bug #261 (ldap_pairget fixes), perhaps it could be added to 1.1.1, too. I'm not using LDAP on my site, therefore I can't test it myself easily.
I know I have been mia for the last few months, so I can probably spare some time to test it... :-)
1.1.2 - upgraded libtool & autoconf??
That isn't pleasant work at all, but I think it should be done. Our current autotools are the worst, and they are not supported anymore by their authors.
Once that's done, the CVS head is starting to look a little anemic...
I don't think so: there's still a lot of cool new features in the server core (IPv6 support, new radrelay, hash tables implementation to name a few of them) and a lot of new modules: rlm_policy, rlm_sqlippool, rlm_expiration, rlm_caching...
What is holding up the new radrelay code from going in? It is a very cool feature for high volume deployments.. Regards -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc