2.4.0 - How Often to Update?
-
Hi Everyone,
I'm running the 2.4.0 beta and it seems very stable. I see usually at least twice a day that there is a new version posted for upgrade. Should I upgrade every time there is a new version? Are there release notes to know what I should be looking at with each release?
Brian
-
How often you update is up to you. If you want to provide a "service" by testing the latest and greatest version, then by all means update every new release.
-
Its a balance between helping test out the versions and the old "if its not broken don't fix it"
Tends to mean I update every 3-4 weeks
-
Thanks for replying. Typically I'm updating whenever I see there is a new release as I'm pretty eager to contribute back. Is there a place to know what I should be looking at between releases? I know that redmine.pfsense.org has a list of open issues for the release, but without some kind of release notes or change log it's difficult to know what I should look at between releases. Anyone know if that exists and if it does where to find it?
-
https://github.com/pfsense/pfsense/commits/master
-
Thanks for replying. Typically I'm updating whenever I see there is a new release as I'm pretty eager to contribute back. Is there a place to know what I should be looking at between releases? I know that redmine.pfsense.org has a list of open issues for the release, but without some kind of release notes or change log it's difficult to know what I should look at between releases. Anyone know if that exists and if it does where to find it?
There are no releases of 2.4 because it's still BETA and therefor no release notes either. The snapshots are taken automatically by a cron job and there are no guarantees that a snapshot includes or misses an important bug fix or a new feature. The only way to track the important milestones is to track the bug reports at redmine and review the changes at github related to the bug reports.
-
I might start updating more regurly now, today I did an update which went through about 7 months worth of code changes, and it didnt go smoothly, with some issues with update the php modules.
I expect I will have less problems in future if I ensure I update often enough that is no big backlog of changes on the update.
-
I might start updating more regurly now, today I did an update which went through about 7 months worth of code changes, and it didnt go smoothly, with some issues with update the php modules.
I expect I will have less problems in future if I ensure I update often enough that is no big backlog of changes on the update.
To be safe, I suggest you download the latest snapshot and do a clean installation. I'm not surprised that there were issues catching up from so far back.
-
i update every 2 days…
the only issue i think is the ipv6 not restarting... but I thinks its comcast...
and ntop doesnt work via webui.. until I go into settings first and hit save then ntop works!
great job guys
-
When I first start running a beta version, I'll update maybe once every two to three weeks… four if I'm being especially lazy. As we get closer to release, I'll update weekly. If there's an issue I've experienced that has been fixed, or something that wasn't affecting me but I want to test the fix for, I'll update sooner.
Then when the release hits, I'll run that for a few months before determining if I want to participate in the next beta. I usually join in for major release betas, not so much for minor ones.
