Releasing 2.1.5 or 2.1.6
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. There is a 2.1.5 trial version on the build server that I've lightly tested, perhaps others should as well. Can we move the next release forward to an official release so we can get a release out to supercede the current version, which to my thinking is 2.1.3 (because 2.1.4 is not identifiable). 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. -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
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.
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.
Do we have a target date? Do we need to get volunteers testing a trial 2.1.6 so we can move forward? -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
John Dennis wrote:
Do we have a target date? Do we need to get volunteers testing a trial 2.1.6 so we can move forward?
The target date is a week or two. As of now (and moving on), the page at: http://git.freeradius.org/pre/ Will contain the latest pre-release tar files. These files may not exist from time to time (as they are rebuilt), but they should be there most of the time. Alan DeKok.
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
participants (4)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Borislav Dimitrov -
John Dennis