Well, I rather not downgrade of course, but I have other things (scripts etc.) that may read or write the config files and changing the owner of these files will require a total overhaul of the file permissions.
I'm sure splitting the ownership is a good idea security-wise, but I would expect such a change to be noted in really big red letters in the changelog, followed by an explaination of what exactly is changed so that preparations can be made.
Have you considered to make the change an option for a couple of releases so that people have time to ajust their environments to this change? You should at least incorporate some kind of check in the installer and alert users that the permissions need to be changed, now it upgrades correctly continues to serve correctly but completely breaks the web console without any direct link to the upgrade.
Most of the users will probably use some control panel or an apache config file, but I was glad with the XML format and have integrated the configuration of vhosts into our intranet. This simple change means that we need to re-think the entire setup and requires a testserver and extensive testing, etc.
In my opinion changes that need a change in the environment require at least a minor version bump, not just a revision increment.
Also, I am really unconfortable with software updates that silently add users to my system. Especially because it choose an inappropriate UID, which I would need to correct by hand.
Last edited by raphidae; 08-27-2009 at 07:29 PM..