FreeRADIUS 3.x roadmap ?
Hi, I found a roadmap of the 2.x branch of FreeRADIUS on the wiki. Is there something similar for the 3.x branches ? More specifically, I need to know if you're going to release the 3.0.8 version in the next weeks. Regards, -- LRS This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Roadmaps are Roadmaps. Show me definitive 2.x release dates. 3.0.8 will be released when ready. Alan has already said (an issue is there are less testers than for 2.x code). Alan
Le 18/03/2015 10:16, Alan Buxey a écrit :
Roadmaps are Roadmaps. Show me definitive 2.x release dates. 3.0.8 will be released when ready.
I agree, I didn't ask for a formal date. I just wanted to know if the plan is to release 3.0.8 in one week, one month or one year. -- LRS This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
On 18 Mar 2015, at 11:50, RESTOUX, Loïc <loic.restoux@capgemini.com> wrote:
Le 18/03/2015 10:16, Alan Buxey a écrit :
Roadmaps are Roadmaps. Show me definitive 2.x release dates. 3.0.8 will be released when ready.
I agree, I didn't ask for a formal date. I just wanted to know if the plan is to release 3.0.8 in one week, one month or one year.
FreeRADIUS has no release schedule. If you wish to take advantage of fixes that will be included in 3.0.8 I suggest you use the current v3.0.x head and create a tag in your local repository to mark the version of the code you're deploying. Creating tags in the upstream repo does not bless the code in any way. No special incantations, no sacrifices of wiffly nosed bunny rabits. The CIT tools get run, unsurprisingly, continuously, on every commit. Coverity gets run daily. There is absolutely nothing special about a code release vs any given commit in the repo, other than it has a number assigned to it. -Arran Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS development team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
On Mar 18, 2015, at 5:03 AM, RESTOUX, Loïc <loic.restoux@capgemini.com> wrote:
I found a roadmap of the 2.x branch of FreeRADIUS on the wiki. Is there something similar for the 3.x branches ? More specifically, I need to know if you're going to release the 3.0.8 version in the next weeks.
We’re probably going to release 3.0.8 in 2 weeks. We do need more testing of the v3.0.x git head. In general, there’s no release roadmap. The releases are done when they’re done. We don’t have resources to have a fixed release schedule. Real life often gets in the way of new features. We do have plans for the 3.1 branch, which will involve some re-architecture of the server core. The goal is to simplify the configuration and code, while keeping it backwards compatible with 3.0. Alan DeKok.
On 03/19/2015 02:54 PM, Alan DeKok wrote:
On Mar 18, 2015, at 5:03 AM, RESTOUX, Loïc <loic.restoux@capgemini.com> wrote:
I found a roadmap of the 2.x branch of FreeRADIUS on the wiki. Is there something similar for the 3.x branches ? More specifically, I need to know if you're going to release the 3.0.8 version in the next weeks.
We’re probably going to release 3.0.8 in 2 weeks. We do need more testing of the v3.0.x git head.
Awesome! I'll try to get that into Fedora.
In general, there’s no release roadmap. The releases are done when they’re done. We don’t have resources to have a fixed release schedule. Real life often gets in the way of new features.
We do have plans for the 3.1 branch, which will involve some re-architecture of the server core. The goal is to simplify the configuration and code, while keeping it backwards compatible with 3.0.
Which one will be the stabilized 3.x branch? Nick
participants (5)
-
"RESTOUX, Loïc" -
Alan Buxey -
Alan DeKok -
Arran Cudbard-Bell -
Nikolai Kondrashov