Release 1.1.0 this week?

[Nicolas Baradakis]

Alan DeKok wrote:

> Nicolas Baradakis <nbk at sitadelle.com> wrote:
> > 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.
>
>   I had fixed *most* of that by moving the TLS stuff to libeap.  But
> your changes fix the rest.

Sorry, I didn't say it correctly. You actually did all the work to fix
the problem. I deleted the remaining libtool warnings and cleaned up
some unused stuff. (and now the CVS head is building fine)

> > 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.
>
>   I'd rather do a 1.1.x every month.  That way we get lots of changes
> moving out the door quickly, and we don't run into the 2.0 problem of
> waiting forever.

Sure. That's a good idea.

> > 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...
>
>  I know... it's just that there are a few things in the CVS head I've
> been avoiding that desperately need fixing.

Sorry, I misunderstood what you were saying in the first place.

On other news, the last minute report for the build issues on Mac OS X
(bug #310) have just been fixed. I hope this is really the *last* patch
before release 1.1.0.

http://bugs.freeradius.org/show_bug.cgi?id=310

-- 
Nicolas Baradakis