On Mon, 2002-04-08 at 09:30, Chad Miller wrote: > > Matthew's right. The rate of development makes it awfully hard to plan > releases. IMO, FreeRADIUS needs a "stable" branch that is pushed towards > 1.0, instead of the whole tree being in a perpetual alpha-state. That > means no EAP, no Python module, no $whiz_bang_untested_feature
That would be awesome! I would like to deploy FreeRadius in production, as an authorization server (keep the allowed IPs for each user in MySQL with FreeRadius) and pushing the authentication to another Radius server (using FreeRadius's proxy feature), but the current status of the source tree kind of scares me. :-/ I mean, for me, if only the MySQL authorization backend and the Radius proxy authentication would be "stable" - that should be theoretically enough. But there's a ton of other things that make me wait for a stable release. Which kind of sucks, because FreeRadius is so cool. ;-) -- Florin Andrei A bug is a feature that can't be turned off. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
