It seems the most annoying aspect of updating from one version of Wowza to another is the arduous process involved in re-modifying all the configurable files that drive a Wowza installation. It is tricky because the files that are already running in the "old" version are themselves modified from the originally distributed files. The new distribution will have files that then have to be modified, but the new files also incorporate the consequences of feature changes that have occurred between the "old" version release and the new one, and these new changes have to be incorporated somehow into the new version as well.
Is there something you guys can do to make this process easier? In an ideal world, you would have a tool that given the release number of the "old" version would be able to apply the necessary deltas to configuration files to bring them up to date. This would involve removing obsolete stuff, adding appropriate defaults for new stuff, and perhaps highlighting and asking the user what to do about things that are just different now.
Failing that, perhaps you could promise that when features are introduced that would require changing configuration files that you would bump the second digit in the release number? That way if upgrading from 3.a.x to 3.a.y we wouldn't have to worry about configuration changes, but going from 3.a.x to 3.b.0 would mean there could be configuration changes, and those configuration changes would be documented in some way that makes the upgrade easier?
At the very least, each time a configuration file undergoes a change for release, that should be documented in the file with a comment like:
"Distributed version modified for release: 3.a.x" and a description of what changed. Previous comments like that should be left in the file to leave an audit trail for people that only update infrequently and may need to accommodate changes across multiple release versions.
What do you think?