Super Stoked for 2.3
-
So much activity! I don't know if I can hold off for 2.3.1 when the time comes for that decision.
-
Now that 2.2.5's past, several of us upgraded our production home systems to 2.3 this week. Some of those really complex. My home system probably the most complex, with multi-WAN, lagg active mode LACP, VLANs, 10 public IPv4 IPs, a slew of IPv6, IPsec, OpenVPN, and more. I prepped a replacement box to swap in just in case, but no need. Flawless switch over.
Still a ways to go, but things are better than I expected for this stage.
-
@cmb:
Still a ways to go, but things are better than I expected for this stage.
It really is looking good - even without a separate column for port number in the filter logs :'( . Congratulations to everyone who has contributed. Eagerly awaiting package migrations.
Would it be feasible to set up a sub-forum (or whatever) for package developers/maintainers to announce the status of their packages for 2.3 - invite testing, feedback, etc?
BTW, does the pfSense team collect any stats on the relative popularity of the various packages - even if only the number of downloads over time? That would be really interesting.
-
Would it be feasible to set up a sub-forum (or whatever) for package developers/maintainers to announce the status of their packages for 2.3 - invite testing, feedback, etc?
The 2.3 board is the best place for that. Don't think there is enough volume to justify another board, though could create a sub-forum for that if there get to be enough posts there (and move them over if it gets to that point).
BTW, does the pfSense team collect any stats on the relative popularity of the various packages - even if only the number of downloads over time? That would be really interesting.
We can count how many times a package is installed from the web server logs. Last I ran the numbers, it was Squid, Squidguard, Snort as the top 3 in that order and everything else a good deal lower than those. I'll have to run those numbers again soon.
-
I just noticed all of the bootstrap tasks have been closed out. I wonder if they're going to move the remaining bugs and stuff to 2.3.1 and get 2.3 out.
-
Not closed out, just moved. Just consolidating everything back into a single project in redmine. When we started the separate Bootstrap project it made sense to keep things separate (it was even outside the main repo at that point), but that's no longer the case.
-
Anyway, it seems a milestone has been reached for the UI overhaul.
-
I wonder if they're going to move the remaining bugs and stuff to 2.3.1 and get 2.3 out.
Doing this would be a mistake, IMO. Some bugs are more important than others.
There are a small number of high-priority bugs that need to be fixed before I'll call for a 2.3-BETA release. There are a larger number of lower ("normal") priority bugs that need to be fixed before we start making release candidates.
The main foci of 2.3 have been the update to the webGUI, the move to FreeBSD's -STABLE branch, the new update system based on FreeBSD's 'pkg'.
Updates are now much smoother/faster, and we'll be able to update subsystems of the system easier. We also made the build system much more like the one in our upstream (FreeBSD). The result is we can implement and test changes, and bring fixes in from FreeBSD and ports much more rapidly.
I update my system at home (*) several times / week, sometimes several times / day (including git syncs). If you look, we even put support into the GUI (and the supporting infrastructure in the system) to allow the git sync to a given branch (normally "master") on update, so tracking the absolute top-of-tree (or any other branch, really) becomes straight-forward.
(*) which has been running 2.3 "in-production" for about a week longer than the others Chris mentions.
-
I forgot about all of the other parts of 2.3, than just Bootstrap. I just assumed the listed bugs were bugs that already existed in 2.2.x.
-
2.3 is looking great so far. Very stable for an Alpha.
Is 2.3 going to be 64 bit only?
-
No. 2.3 will still run on 32bit, however its been recommended for a while to run x64 if possible.
There are plans to drop support for 3.0
-
I remember seeing that (dropping 32bit) but I couldn't remember if it was for 2.3 or 3.0. At any rate I love pfsense, just trying to judge when I'm going to be forced to upgrade my old hardware even though I think it's kinda cool that 14 year old hardware can still have a purpose.
