22.09???

[techpro2004]

Just wondering what happened to 22.09. Are we going to keep pushing back future builds because the previous release was late? If so, in a few years we may be 5-10 releases behind. This is a dangerous path.

[stephenw10]

If that needs to happen, yes.
Would you rather we rushed the development through in order to make some numbers line up? Maybe forget testing? Or we could just release in September with no development?
Those things are never going to happen. Obviously we would rather make the targeted 3 releases a year but it's not the end of the world if one has be pushed back.

Steve

[MORGiON]

@techpro2004 not doing it would be the dangerous path

[gabacho4]

I can understand the thrill of upgrading to a new version with some improvements or new capabilities. However, asking Netgate to rush a release is not the way to go. If I recall right, Jim Thompson admitted they did this with the original WireGuard implementation in pfsense because there was so much excitement and demand for it. However, it had some significant issues that were later exposed. I personally had two SG-5100s that ended up dead in the water due to a kernel panic that was later confirmed to occur if certain conditions existed. It was a small inconvenience on my local router. It was a MAJOR problem on the router that is 7000 miles away. It was partly my fault; my previous OVPN or IPSec solutions worked well for years…I just got excited to use the awesome WireGuard implementation. Ouch. And Netgate took a very mean beating as a result of the issues its user base had. So, as long as your router is pushing packets and there are no unaddressed CVEs, be happy and let the process work.