1. Aleph Version Maintenance

2. Version Maintenance -2--2- Requirements for Aleph 500.14 Stability Control Minimum changes for user Systematic patch application Automate where possible

3. Version Maintenance -3--3- Requirements for Aleph 500.14 Stability –deliver a fully tested version –minimize future fixes Control –keep ‘clean’ version –replace only wrong files Minimum changes for user –keep files and tables structure –less fixes to be applied

4. Version Maintenance -4--4- Requirements for Aleph 500.14 Systematic patch application –about every 60 fixes –available documentation –fixed process for upgrade Automate where possible –prepared scripts for application

5. Version Maintenance -5--5- Solutions for Aleph 500.14 New Quality Control Group –stability –control Existing rep_change mechanism Patch Control –systematic patch application –automated processes

6. Version Maintenance -6--6- Patch Control “500.14.2 1 ” –first production version –control passes from QC to Support –already has many rep_changes before production release

7. Version Maintenance -7--7- Patch Control “500.14.2 n ” –subsequent production versions –available as version or incremental patch –will have ~60 rep_change additions per patch

8. Version Maintenance -8--8- Patch Production at EXL/QC 500.14.2 n version –closed by QC according to support group request –based on 500.14.2 n-1 –additional rep_changes applied –gzipped tar file of the complete version for every platform

9. Version Maintenance -9--9- Patch Production at EXL/QC 500.14.2 n patch contains –new/modified files from 500.14.2 n-1 –new executables (per platform) –backup list –backup script –documentation one gzipped tar file for all platforms

10. Version Maintenance -10- Application of patch Performed by supporting agent Place patch files in $aleph_dev Backup files to be changed Open patch to target Apply library setup changes according to documentation

11. Version Maintenance -11- Patch application policy Must be applied consecutively Can apply 1-4 patches at one session Try to maintain all customers at the same patch level Avoid individual fixes where possible

12. Version Maintenance -12- Documentation New “How to” document for application Description of each patch on web support interface “rep_change patch 4” will list patch 4 rep_changes only “rep_change patch 4 readme” will list the readme file of patch 4

13. Version Maintenance -13- Looking inside cd /aleph/patch14.1 ls 14.1.03/ 14.1.03_other_servers/ Show on server