2.2.3 Inquest

ivor

Hello. I don't mean this to be a hit and run, I am simply too busy to check in as often as I'd like.

Let me reset the message. If you scan down the subjects of the Installation and Upgrades area of the forum and look at how many are 'broke or degraded since 2.2.3', it's more than 1 or two. In fact at the time of writing, I think I can see possibly 6 (not including this) on the first page alone.

What I'm suggesting is that it may be a good idea to consider what can be done to reduce this in the future. More testing? More testers? Different test scripts or test harness?

This was intended to help build up pfSense
andy

PS, For the record its the squid package that's causing me problems, but this isn't the forum.

You are aware that pfSense is being ran in productions worldwide? So we're talking hundreds of thousands installs? Not to mention thousands of installs of pfSense / Netgate hardware as well?

kejianshi

At every upgrade and new release there are always many many "The update broke my pfsense" threads.

Some are actual pfsense issues

Some are hardware issues

Lots are issues with the guy at the keyboard.

No such thing as a release that goes perfect.

Even if the code were 100% perfect, just when you assume its idiot proof a better idiot would come along.

Just saying. There are always problems.

robi

And the funny part is that such problems (and even worse) usually occur in similar situation at most commercial products too.

kejianshi

One thing I've learned with pfsense, linux, windows, whatever…

Don't install any feature unless you NEED it.

The cleaner and simpler you keep an install the less problems you will have.

Thats universally true.