22.01 ETA still holding up?

keyser

The name 22.01 implies January 2022 - is that still the expected ETA of the next pfSense+ release, or will 22.02 be the “ghost moniker” of 22.01 release version?

johnpoz

@keyser The latest info both the email newsletter they sent out, and via twitter 22.01 is still on track for Jan.. I have not seen anything saying or suggesting even that is not the case still.

stephenw10

Yup as far as I know still on track. Some things are beyond our control there but I'm not aware of anything yet.

Steve

beachbum2021

I updated to 22.01.r.20220113.1946

Not seeing the analytics features advertised to be available. Am I miss-understanding this update?

johnpoz

@beachbum2021 what feature?

https://docs.netgate.com/pfsense/en/latest/releases/22-01_2-6-0.html

Where did you see talk of some analytics feature?

mcury

@johnpoz said in 22.01 ETA still holding up?:

https://docs.netgate.com/pfsense/en/latest/releases/22-01_2-6-0.html

uau, very big list of improvements and bug fixes :)

johnpoz

@mcury yup lots of good stuff, but not seeing anything that jumped out about any sort of analytics.. And I toggled through all the added: lines and searched for analytics etc.. Nothing jumped out at me.. So curious what specific feature he is referring to, and where he saw it stated?

mcury

@johnpoz said in 22.01 ETA still holding up?:

So curious what specific feature he is referring to, and where he saw it stated?

I don't see anything like that too..
Looked everything..

I'll probably do a clean install here..
As soon as its installed, I'll disable the log compression (sg-3100 not using ZFS).
Glad they fixed the php interpreter for the sg-3100, the dns resolver failing to load (that usually affects people that runs pfblockerng with python mode enabled and specially when restoring configs).. lots of ipsec news :)

SteveITS

@mcury said in 22.01 ETA still holding up?:

As soon as its installed, I'll disable the log compression

Not sure why you'd wait a version...? (you can do it now)

mcury

@steveits said in 22.01 ETA still holding up?:

Not sure why you'd wait a version...? (you can do it now)

Just did.. No reason to wait indeed..

johnpoz

@mcury said in 22.01 ETA still holding up?:

I'll probably do a clean install here..

Yeah prob same here, I think there was some changes to overall zfs stuff that was scheduled for 21.09, etc. Something to do with the overall layout.. something to do with root or partitions..

beachbum2021

@mcury i deleted the last two emails i received from pfsense so i cannot confirm what thought i read. sorry for the confusion...the release page clearly doesnt show what i thought i read.

keyser

@johnpoz They are cutting it close if january is still ETA…

luckman212

@keyser And there's a mantra in devops about "Don't Deploy on Friday" etc. So that leaves just Jan 31 hah.

stephenw10

Indeed it does.

johnpoz

@keyser I have been flogging them daily, you know to make sure their morale stays high..

I have to believe they want nothing more to release per their announcement, especially after 21.09 not being released.

But as always I am sure the release will happen when its ready..

I do believe there was another tweet mentioning something about supply chain and all that.. There was this tweet on the 15th

https://twitter.com/pfsense/status/1482479419377733633?cxt=HHwWgsCyra3L6ZIpAAAA

luckman212

keyser

@johnpoz Wonder what happens now? I get that product quality is paramount (as it should be) and there will be no release until it is ready, but..

1: Is there a risk they will pull this release like they did for 21.09 and aim for 22.05 instead now?
2: Will it release here in february or match when it’s ready, but still with the 22.01 name, or will it be renamed to 22.02 or 22.03?

I hope it’s not the former. I’m looking forward to all the IPsec fixes and especially the ZFS option to make the small ARM devices a little more poweroutage resistant. They are REALLY sensistive to corrupted filesystem bootloops in my experience.

Considering that Netgate is looking for more income/customers, my advise would be to start communicating a bit more. Things like 21.09 being pulled with some random twitter message but no official statements, and now this delay without a hint of explanation. I don’t think that helps with customer confidence.

johnpoz

@keyser all good points - I wish I had answer for you. Lack of communication is disconcerting to be sure.

stephenw10

@keyser said in 22.01 ETA still holding up?:

Is there a risk they will pull this release like they did for 21.09 and aim for 22.05 instead now?

Nope.

@keyser said in 22.01 ETA still holding up?:

Will it release here in february or match when it’s ready, but still with the 22.01 name

Yes.

We were on schedule for release yesterday but found a bug over the weekend that none of us could live with. That had now been fixed.

Real soon now....