Oops, one more thing. I hope it’s not too late!
Currently, I believe that IT has Zend_Framework code stored in a centralized location so that users don’t have to consume quota for that. It would be great if that service was mentioned in the SLA.
For completeness’ sake I would suggest something like this (using semi-fictitious versions):
- /path/to/zend/1/
- 1.12.13/
- 1.12.14/
- 1.12.15/
- etc.
- /path/to/zend/2/
- 2.4.7
- 2.4.8
- 2.4.9
- etc.
In other words, keeping past versions as well as the latest versions.
These don’t have to be full packages, but just the basic deployment code.
In addition, it might be useful to have something like /path/to/zend/1/latest that’s a symlink that always points to the latest version, whatever that is. So, in for the examples I gave above:
- /path/to/zend/1/latest -> /path/to/zend/1.2.15
- /path/to/zend/2/latest -> /path/to/zend/2.4.9
Because both versions are fairly stable, developers don’t have to worry (much) if they use latest, and rely on IT to update the framework as needed. Having the ability to point to any version provides maximum flexibility, if needed.
Please let me know if any of this is unclear.
Thanks!
Greg