Occasionally the EWAG Core Group (ECN/ECO) will make changes to the framework that runs the Engineering Web Cluster. Examples include:

• Changing Zope versions
• Upgrading Zope products
• Adding new Zope products

These upgrades can potentially effect the web sites hosted on the Engineering Web Cluster. Prior to making these changes they are placed on a test server for evaluation. Historically the EWAG Core Group has been responsible for testing. Use of the web has increased to the point that the Core Group cannot monitor the impact of all changes.

This document defines a policy for upgrading and testing that includes review by the entire EWAG group.

Notification

Once the Core Group has upgrades ready for group review a post will be made on the EWAG Forum and email notification will be sent to the EWAG mailman list. Notification will be sent at least five working days prior the proposed upgrade and will include:

• Overview of changes
• List of things to check
• Proposed upgrade date

Testing

Upon receiving a notification of a proposed change, please access the test server and review the sites you maintain.

Feedback

Send any problems you notice (pages that no longer work) to the EWAG mailman list and the core group will correct the problem on the test server. Any feedback requiring additional changes will result in a new notification being sent and the proposed upgrade date being pushed back to compensate.

Exceptions

The EWAG Core Group reserves the right to make emergency upgrades that are required to maintain the functionality of the College of Engineering's web presence without the adhering to the above testing proceedure. Such upgrades include:

• Security Patches
• Fixing bugs not caught during a previous testing cycle