22.01 ETA still holding up?
-
@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
An intelligent man is sometimes forced to be drunk to spend time with his fools
If you get confused: Listen to the Music Play
Please don't Chat/PM me for help, unless mod related
SG-4860 24.11 | Lab VMs 2.7.2, 24.11 -
-
@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.
Love the no fuss of using the official appliances :-)
-
@keyser all good points - I wish I had answer for you. Lack of communication is disconcerting to be sure.
-
@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....
-
@stephenw10 real soon has been said all over these forums and Reddit for days if not weeks. Itās not a good look.
Edit: I contribute, I buy appliances, I drink the pfsense kool-aid. But implementation with this āoh one more minuteā is tough tough tough.
-
Perhaps Netgate should consider labeling the releases "22.Next" instead of a month number, to "resolve" this. :)
Personally, I'd rather have "good" than "on time."
Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
Upvote š helpful posts! -
@steveits when customers have maintenance windows and they pay for support, you sort of need both or people get touchy.
-
@steveits said in 22.01 ETA still holding up?:
Perhaps Netgate should consider labeling the releases "22.Next" instead of a month number, to "resolve" this. :)
Personally, I'd rather have "good" than "on time."
Yeah, that is probably a good idea. I have certainly changed my perception and expectations of netgate this last year since the advent of pfSense+ and the whole Wireguard situation.
Unfortunately not in a positive way.Initially I though: āokay, I can live with thatā, and decided to go all in on factory appliances - to be on the safe side with plus, added features and the more business like approach it signalled.
I must say it has been a huge let down in predictability and especially in missing communication ever sinceā¦
Edit: Wonder how long this last āreal soon nowā will be. Hopefully not months like the first ones, and weeks like the latter ones, have been so far.
-
Just curious, is there a feature or fix that is driving the anxiety with the update being late?
Mine is running fine and I am not waiting on a feature. I do get anxiety when installing updates...
-
@andyrh said in 22.01 ETA still holding up?:
Just curious, is there a feature or fix that is driving the anxiety with the update being late?
Mine is running fine and I am not waiting on a feature. I do get anxiety when installing updates...
Yeah for me there is: ZFS support on the small ARM appliances.
I love those appliances from a performance/power perspective (especially the SG-2100). But they are really sensitive when it comes to power outages. My experience is that around 10% of all power loss situations causes a boot loop because of a corrupted filesystem.
I have a bunch of them purchased to be deployed in small remote sites without UPS support. I hope ZFS will prove I can skip the investment in UPSās for every location.
But the locations are waiting, and i cannot wait much longer. This has already been delayed FAR too long. -
@keyser, mmmm your point seems interesting could you be so kind as to share a little more details about your configuration? schematics etc...what is the purpose?
-
I wish I could tell you 100% when it will be released but until it passes testing I cannot.
I can say you would have been far more disappointed had it been released with any of the issues we found and fixed that have caused delays.
Internally it is looking good right now.
Steve
-
@stephenw10 said in 22.01 ETA still holding up?:
encontramos y solucionamos que causaron retrasos.
how I can help?
-
@silence said in 22.01 ETA still holding up?:
@keyser, mmmm your point seems interesting could you be so kind as to share a little more details about your configuration? schematics etc...what is the purpose?
?? The configurations are fairly simple, but the devices still seems to touch the disk/ssd enough, that quite often a power outage will leave the FS openended and corrupted.
ZFS uses an intirely different strategy for writing to disk. It always allocates free sectors to write/overwrite data, and then completes a write by updating filesystemtable/pointers in the current datainstance - the old data and pointers are still there - not touched -, but they now belong to the latest snapshot.
Once flushed, the filesystem is consistent. If a flush is not made, no changes that leaves existing filesystem corrupt has been made. So hopefully that will help keeping the ARM devices from boot looping because of inconsistensies in the filesystem.
I understand specific files can still be logically corrupt, but thatās easier to survive - especially because ZFS also has the previous snapshot to read from. -
@keyser Oh okay ! I also wait for the next version but I don't have any problems at the moment.
-
@stephenw10 said in 22.01 ETA still holding up?:
I wish I could tell you 100% when it will be released but until it passes testing I cannot.
I can say you would have been far more disappointed had it been released with any of the issues we found and fixed that have caused delays.
Internally it is looking good right now.
Steve
Hi Steve.
Itās not a disagreement because I donāt want releases with known bugs either. Software quality is paramount.
Iām just not happy with Netgate settings public schedules and release names that they are not remotely close to maintain. If you set them, you need to inform and update the customerbase well ahead of any kind of delays - and include a new ETA to the best of the current knowledge.
If you are so tightlipped with ANY guessing on release date now, how can you guesstimate the planned release schedule and planned release names?Either keep us informed whenever deadlines starts to be threatned, and then keep us in the loop during the delay.
Otherwise announce a FULL stop to the planned release schedule/kill the monthly build name indicator, and go back to itās ready when its ready.
You are setting expectations with the current strategy that netgate cannot cash in. The current strategy can only create dissapointment (There is no possible win).Anyhow :-) Iāll wait patiently for a few weeks more until it is presumably ready.
-
redmine has only 23 open issues, all of them in feedback status.
2.6 rc hasn't changed 2.6.0.r.20220124.1828 for the last two weeks.
So its close. Very
And since we all love it, next Monday(2/14) is the most probable date. -
@netblues itās been at 26 open for weeks. Commits in GitHub as recent as 1/31. Donāt use redmine as a gauge for release, youāll be disappointed.
-
@herozero I know, I'm aware of the rate.
Still it Is very close to be released.
I'd bet this month. Finger's crossed.(on the other hand rc has been quite stable too.
No, I wont put rc anywhere critical or without easy supervision. But then I wont be putting 2.6 telease anywhere until at least two weeks have elapsed and the forum isn't on fire too)
