2.4.5 date?
-
Can't understand people here. Are any of you thinking hitting F5 every 5 minutes and spamming "release when!?" and complaining about even more tickets will get you the release any sooner? They could release right this moment. And everyone would bitch back how they could do such ab shitty job releasing such a buggy release etc. etc. It's completely normal that when working on burning down the last tickets new issues arise and bugs pop up. Better now in testing then in production.
What do you really want? A stable and safe to upgrade 2.4.5 release or a rush-job so you get your new shiny version number on your dashboard?
If it's the last one - just install the 2.4.5 snapshots. You'll even get a new release number every few hours when new releases were built 
-
Counting issues is a poor metric for how close we are to a release, especially when the count is this low.
A little trivia:
Of the 12 issues remaining open on 2.4.5:
- 6 are in feedback state in need of testing (And one of those is an issue in a package which is not a blocker)
- 4 are release-related tasks (write release notes, SAs, blog post, update docs) and are not bugs
- 2 are actual bugs that remain to be solved
As with any release, if you want to see it released faster, test the snapshots and report any issues you find.
Nothing short of confirming things work properly will speed up the release process.
-
Would love to test.
On a live system, with captive portal users ...
I'm waiting for Luiz .... -
And then there were only 5 issues left. Are we looking at this week or next? Thanks.
-
Still no ETA. There are some issues yet to work out for captive portal and our various hardware platforms. I would hope to at least see an RC sometime next week but don't quote me on that. We don't know how long it will take to iron out the remaining issues for certain.
-
While I understand it is very rough, Thanks for the rough idea.
-
@Gertjan said in 2.4.5 date?:
Would love to test.
On a live system, with captive portal users ...
I'm waiting for Luiz ....Captive Portal is OK on the latest snapshot. Time to test. :-)
-
@jimp said in 2.4.5 date?:
Captive Portal is OK on the latest snapshot. Time to test. :-)
UP and running - first impressions :
Probably not important - but I have these now :
Logging to the remote syslog server (he lives on LAN at 192.168.1.4 port 514 UDP) works well - pfSense settings are as they are for the last decade :
Also :
radvd doesn't look happy now :Although my IPv6 is up an works as usual (a he.net tunnel setup using a gif interface etc)
Also : the patch to have portal users not thrown out of the ipfw tables when captive portal settings are changed is still needed ??!!
This one https://github.com/pfsense/pfsense/compare/RELENG_2_4_4...Augustin-FL:fix-reconfig-for-2-4-4.diff ( @free : isn't / wasn't it merged already - or only against 2.50. dev ?) -
any idea of what day this week we will see the rc and how long they usually last before. a release? Thanks
-
Update : using 2.4.5 2.4.5.a.20200119.2153
See https://forum.netgate.com/topic/149828/freeradius3-0-15-7_9-2020-01-20-its-stops-can-t-find-libmysqlclient-so-20 for a FreeRadius 0-15-7_9 issue.
Still seeing massive :
in the General > System log.
I'm using a syslog UDP port 514 for years now.
Logs are received on that 'syslog' server. -
@techpro2004 said in 2.4.5 date?:
any idea of what day this week we will see the rc and how long they usually last before. a release? Thanks
No. It'll be out when it's ready, not a moment sooner. There is no ETA. And there is no 'usual' time between RC and release.
Have patience. It'll come. If you are that impatient, run snapshots and test.
-
I have a idea, how about netgate starts a betting pool, whoever guesses closer to the date wins a sg-1100. It would be great for PR and would bring awareness/new customers to pfsense.
-
No.
-
This thread has outlived its usefulness. Locking.