Pfsense CE 2.7.0 Release (?)
-
Quite a few of those open tickets will be long term issues that can be moved to the next version when we branch for 2.7 so it's not entirely accurate.
Steve
-
@stephenw10 I was just pointing out that to many people it seems like it's taking a long time for 2.7.0 to come out and the needle isn't moving (only going from 89%-91% in this case). In this thread there are complaints, talk of jumping ship, and accusations of motivations. I just don't get it. When you look at the numbers over time it is clear the developers are working hard and getting things done. I know the Roadmap is accurate but it is just a snapshot in time. If you don't compare it to what it has shown in the past you don't see just how far it has come and you'd think it's been stagnant at 90% for a month, which isn't the case. If some of those tickets will be addressed in later patches and releases then it's even closer.
The only reason I personally care about 2.7.0 is for the i226 support. If that support was added to 2.6.0 I wouldn't even be reading up on 2.7.0. I don't need another version number to feel like I'm keeping up. Many of my boxes skipped the 2.5.x line entirely (due to the pandemic and the DNS issues early on) and have gone from 2.4.x to 2.6.0. I trust the team and the project.
One side note, should we read into the fact that no new subversions of 2.6 were released? Is the goal to have a main version like 2.6.0 and just update via the new(ish) patch manager instead of minor releases? Or is just coincidental because the focus went into 2.7.0 with all its major changes?
-
Sorry I typo'd that! I meant that the number of open tickets is likely to go down significantly as we approach a 2.7 release so you can't use just that figure to look at when a release might happen.
After 23.05 is released we will be looking at the timing. At that point you will be able to upgrade to Plus from current 2.7 snapshot again. Both will be on php82.Steve
-
@stewart said in Pfsense CE 2.7.0 Release:
should we read into the fact that no new subversions of 2.6 were released? Is the goal to have a main version like 2.6.0 and just update via the new(ish) patch manager instead of minor releases? Or is just coincidental because the focus went into 2.7.0 with all its major changes?
I'm not Netgate, but the System Patches package does allow for updates to any PHP code. Could be they didn't need any. Binaries would presumably need a version bump.
After 2.6 was released Netgate delayed then skipped 22.09 because of the change to FreeBSD 14 and PHP 8. If those types of changes are not being made especially at the same time then newer releases would be much easier to manage/produce.
Personally I'm not concerned. As you imply, few people need shiny new features on their router. :) Drivers are a notable exception. Per https://www.netgate.com/blog/pfsense-software-is-moving-ahead it sounds like CURRENT is more likely to have drivers for newer hardware going forward.
-
@steveits Other than some OpenVPN certificate issues that can come after an upgrade 2.6.0 has been solid. And we haven't had any issues with new 2.6.0 installs either (although I'm wary of the whole DNSSEC/SSL issues with Quad9). There have been bumps over the years but ultimately pfSense has been very reliable for us. Certainly no more troublesome than some of the other vendors we've used in the past.
-
@steveits a router indeed doesn’t need to be bleeding edge with all the newest features. However it needs to be secure. And being based on an EOL distro is a security concern. It’s not an immediate threat, but it should really be updated ASAP. When it takes this long, I think it is perfectly normal people start getting concerned.
-
Blog entry from today, no word of the CE version only to moving forward to pfSense Plus:
https://www.netgate.com/blog/pfsense-plus-software-version-23.05-rc-now-available -
-
This thread should be locked tbh.
-
@stephenw10 said in Pfsense CE 2.7.0 Release:
It is now possible to upgrade from 2.7 to 23.01
Just to share, I tried this over last weekend and ended up with a failed webGUI. It had an IP and I could ping it; however, after several attempts to relaunch or restart the webGUI nothing. I discovered the failure looking closer at the boot up script then saw the failure stated. Ended up reinstall v2.6 then upgraded to pfSense plus on my private cloud box.
-
Yes, it was possible at that point but there is now a php mismatch since 2.7 moved to php82.
When 23.05 is relased it will be possible to upgrade to that from 2.7.
-
@fireodo said in Pfsense CE 2.7.0 Release:
Still at 91%:
Yes, but look at the change in numbers. It isn't stagnant. In the last 5 days there have been 8 tickets opened and 7 closed. It isn't like they've been sitting on the same number of tickets and it isn't going anywhere. Once new tickets stop coming in, or at least slow down, they will be able to work on the outstanding ones.
@slu said in Pfsense CE 2.7.0 Release:
Blog entry from today, no word of the CE version only to moving forward to pfSense Plus:
https://www.netgate.com/blog/pfsense-plus-software-version-23.05-rc-now-availableAs @stephenw10 stated earlier, the focus will move to 2.7 once 23.05 is released. And if it is between 23.05 and 23.09 then I would expect 2.7 maybe to release sometime around July or August. I could be way off but that's my guess off of what I've been able to see.
@silliewous said in Pfsense CE 2.7.0 Release:
@steveits a router indeed doesn’t need to be bleeding edge with all the newest features. However it needs to be secure. And being based on an EOL distro is a security concern. It’s not an immediate threat, but it should really be updated ASAP. When it takes this long, I think it is perfectly normal people start getting concerned.
I thought that 2.6.0 was based on the Stable branch of FreeBSD12 so it should be supported until the end of the year, no?
-
@nimrod Not until there's a release -- users will just create a new one. I see a new reddit post every 10-15 days asking about it regardless of the presence of previous ones.
-
@stewart said in Pfsense CE 2.7.0 Release:
As @stephenw10 stated earlier, the focus will move to 2.7 once 23.05 is released. And if it is between 23.05 and 23.09 then I would expect 2.7 maybe to release sometime around July or August. I could be way off but that's my guess off of what I've been able to see.
Oh I missed that, thank you for the hint.
We like pfSense software, appliances and the most important the direct contact here in the forum!
-
Can you edit the title of this post so it ends in a question mark? Otherwise it looks like an announcement.
-
In my humble opinion, the 2.6.0 is stable and without serious flaws. The 2.7.0 will be better debugged than the Plus versions because everything that goes into the Plus is also benefic for CE. So I think we should be patient.
Just my 2 Cents,
fireodo -
@fireodo said in Pfsense CE 2.7.0 Release (?):
In my humble opinion, the 2.6.0 is stable and without serious flaws.
And this for sure!
The 2.7.0 will be better debugged than the Plus
versions because everything that goes into the
Plus is also benefic for CE.2.7 is really nice to install, also it matches "faster"
if you hit something in the WebGui menue, it is
like a bit stronger acting and I mean there will be
more changes under the "roof", then we might
imagine from.So I think we should be patient.
Me too. But both (2.7. & 23.05 RC) went now fine
to install and also fine running without any greater problems and for home usage it might be not worth
testing them out. -
@Dobby_ I can see that 2.7 https://redmine.pfsense.org/versions/70
Is there a release date?
-
@Waqar-UK said in Pfsense CE 2.7.0 Release (?):
Is there a release date?
Only historical after it has happened.
As for predicting the future, your guess is as good as anyone else's guess. -
Release Candidates of pfSense CE 2.7.0 and pfSense Plus 23.05.1 Software Now Available
The Release Candidate (RC) builds of pfSense
CE software version 2.7.0, and pfSense Plus software version 23.05.1, are now available. As we prepare for their final release (currently planned for June 29) we invite you to try out the release candidates and share your feedback with us.
