I think we're about ready to release 1.0.3. Comments? Objections? Alan DeKok.
Go ahead. I'm still not ready with the eap-tls code. --Mike ----------------------------------- Michael Griego Wireless LAN Project Manager The University of Texas at Dallas Alan DeKok wrote:
I think we're about ready to release 1.0.3. Comments? Objections?
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
That's good to know. Something said a while back made me think that it was intended to go into 1.0.3, and it seemed like much too big of a change for a minor release. --Mike ----------------------------------- Michael Griego Wireless LAN Project Manager The University of Texas at Dallas Alan DeKok wrote:
Michael Griego <mgriego@utdallas.edu> wrote:
Go ahead. I'm still not ready with the eap-tls code.
Ok. That's for 1.1.0 (or 2.x?) anyways.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
On Wed, Jun 01, 2005 at 01:39:04PM -0500, Michael Griego wrote:
That's good to know. Something said a while back made me think that it was intended to go into 1.0.3, and it seemed like much too big of a change for a minor release.
That may be because I announced that I plan to implement gnuTLS support based on your eap/TLS changes, and have a long-standing bug in Debian to port 1.0.2's OpenSSL dependancy to gunTLS as well. Maybe a hopeful user (I get a few of those a month looking for ways around the license conflict) conflated the two? I'm happy for 1.0.3 to be shipped as is, although it's too late for Debian/sarge, and can't spend long in Debian/sid after the release as libtool1.4 will be going away as soon as we can manage it. (This may lead to me packaging a snapshot of 1.1.0... >_<) -- Paul "TBBle" Hampson, on an alternate email client.
Paul.Hampson@PObox.com (Paul Hampson) wrote:
I'm happy for 1.0.3 to be shipped as is, although it's too late for Debian/sarge, and can't spend long in Debian/sid after the release as libtool1.4 will be going away as soon as we can manage it. (This may lead to me packaging a snapshot of 1.1.0... >_<)
Ok. Can you get the release_1_0_3 tag set up, and update the various scripts/spec files to indicate the new release version? I've updated configure.in, but haven't re-generated the configure scripts. Once you do that, I'll check out release_1_0_3, build a tar file, and put it on the web site. After that, I think we can drop the discussion of 1.1.0, and move directly to a 2.0 release. The server has enough changes to warrant a bump in the major version number. Alan DeKok.
participants (3)
-
Alan DeKok -
Michael Griego -
Paul.Hampson＠PObox.com