2.1.8 and 2.2.0

[Ruslan Shevchenko]

I guess, that better name 2.2.0 as 2.2.0-beta ([release 2.1.8 and
2.2.0-beta at same time, later rerelease  2.2.0 during next month or two)



>   Is it worth having two versions of the server?  i.e. releasing 2.1.8
> *and* 2.2.0 at the same time?
>
>   The reason is that current "stable" branch contains some fairly major
> changes (TCP), and more are on the way.  The next things involve
> changing the internal API, which pretty much mandates a 2.2.0.
>
>   However, there are also a number of bug fixes which could go into
> 2.1.7 and any following release.
>
>   The question then is, do we want to have BOTH:
>
> 2.1.8 = 2.1.7 + bug fixes ONLY
>
> 2.2.0 = major new features + any fixes
>
>   OR, do we want to give up on 2.1.8, and just release 2.2.0?
>
>   There are pros and cons both ways.  Having a stable 2.1.8 is good.
> But maintaining two versions could confuse people.
>
>   Alan DeKok.
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/devel.html
>