aland at deployingradius.com
Wed Dec 2 11:59:01 CET 2009
John Dennis wrote:
> We're trying coordinate our release schedule for our next version of
> RHEL (RHEL 6.0). As it stands now RHEL6 will release with FreeRADIUS
> version 2.1.7. But it takes us a very long time to prepare a new RHEL
> release and in the interim there may be an opportunity to upgrade the
> version of FreeRADIUS in RHEL6 to something newer should you decide to
> make a new release in the next few months.
I plan on releasing 2.1.8 soon. It will be 2.1.7, plus a number of
bug fixes, but *without* any new features.
> I seem to recall a discussion that the next significant release will be
> 2.2.0. Is that still correct? Do you have an anticipated release date
> for that? What major new features and/or bug fixes do you anticipate
> being in it?
The TCP work will go into 2.2.0. I'm also waiting for some other
changes for 2.2.0, which require changing the internal API quite a bit.
The bad news is that old modules won't work any more. The good news is
that the server will be able to handle VENDOR codes over 32K. Since
IANA is already handling out codes over 32K, this change is needed for
any "long term support" version of the server.
I would prefer to release 2.2.0 in January.
> I ask these questions because I might be able to ask management to
> anticipate we will need to rebase the version of FreeRADIUS to something
> newer in RHEL6 than the current 2.1.7. But to do so I have to provide
> dates and the supporting reasons why this would be a good thing to do.
I would say 2.1.8 this week. I'll put up a proposed release shortly.
More information about the Freeradius-Devel