Sriram Natarajan wrote: > > 1) What is the level of incompatibility between minor releases. Based on > Apache 2.0 and Apache 2.2 > http://httpd.apache.org/docs/2.2/upgrading.html > > It seems to me that the incompatibility between these minor releases is > not very much a big deal and can be handled with a post install script. > Do you guys agree ?
IMO that is indeed a key question. If the incompatibilities can all be handled by a script after upgrade, it is a manageable problem. The 2.4 upgrade can overwrite /usr/apache2 and the script can do whatever it needs to do so everything works as before and there is no need for multiple versions which simplifies everything. If the upgrade can't all be scripted, a customer may be left with a dead server that doesn't start (or work properly) after the upgrade, which violates the Uncommitted stability level that 2.2 was given[1]. Sounds like the external modules are the main sticking point. If a future user has a 2.2 install with some external modules made incompatible by the 2.4 upgrade, the script won't be able to fix that. Thoughts? This does assume 2.2 interfaces are Uncommitted. They could be made Volatile in which case the above issue is not an issue as far as stability contracts (of course it still results in an annoyed user). But there has been reclutance in using Volatile. [1] Assuming upgrades during the same minor release family, say S11, which is the context of this discussion. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
