As things stand, any customer upgrading from 10.2 to 10.3 might experience post-upgrade functionality issues.
Two things would help.
Specific list of parameters whose default values have changed.
Modify installation process so that, if a value is changed in the menu, that change is honoured in the resultant pb.settings file.
For example, the default value for "ssl" used to be "no" but is now "yes".
If the pbinstall menu option is used to change "ssl" from default "yes" to "no", then the resultant install script should ensure that the corresponding entry in pb.settings is:
Simply commenting out an entry that contains a default parameter/value assignment is not sufficient to ensure that the chosen configuration gets applied