Releasing 2.1.5 or 2.1.6

[Borislav Dimitrov]

I noticed this version mismatch too: radiusd -v returns 2.1.5 when  
built from the 2.1.4 tarball.

On 22.04.2009, at 17:25, Alan DeKok wrote:

> John Dennis wrote:
>> I'd like to package up the current release but I can't because the
>> current tar files have version problems. What is currently on the
>> download link is 2.1.4 but builds as 2.1.5. There have been two
>> different versions of the 2.1.4 tar file. This means we can never
>> release a 2.1.4 RPM because it's versioning is ambiguous. IMHO the  
>> 2.1.4
>> release should be considered defunct.
>
>  Yes.
>
>> P.S.: We also need to be careful, if what becomes 2.1.5 is not  
>> identical
>> to what's in the 2.1.4 tar file we should go to 2.1.6 because we  
>> won't
>> be able to disambiguate between a 2.1.5 built from a 2.1.4 tar file  
>> and
>> the actual 2.1.5 built from a 2.1.5 tar file. This means the next
>> release should probably be 2.1.6 with 2.14 and 2.1.5 marked as  
>> suspect
>> in the changelog.
>
>  The next release will be 2.1.6.
>
>  Alan DeKok.
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html