Aeon upgrades are generally triggered by the Atlas team through an email to Core Systems and the Product Owner. Upgrades can break existing functionality so should be implemented on the test server and the client/webforms should be tested prior to implementation on production.
Client installation files are stored in the Atlas/Aeon folder on Sharepoint
Instructions for updating Aeon are the same as a new client installation.
Upgrading Aeon is a multi-step process:
- Atlas contacts product owner
- Product owner reviews release notes and sends email confirmation to Atlas
- Atlas upgrades test server and client
- Product owner coordinates testing using the Aeon QA testing spreadsheet (TBD)
- Product owner determines upgrade window in consultation with desktop support and archival repositories and sends confirmation email to Atlas
- Atlas sends upgrade confirmation with new client installation file
- Product owner downloads installation file and uploads to the Aeon folder in Sharepoint and moves the previous version install file to the deprecated folder
- Product owner sends email to the Arch-systems listserv confirming the Aeon downtime window
- Repositories submit ticket to desktop support (with at least 2 days notice) requesting client upgrade for shared computers at reference desks. The ticket must include the upgrade window and the computer name/location.
- Desktop support confirms access to the shared computers and puts the ticket into a pending status.
Morning of upgrade
- Atlas updates Aeon server and sends all-clear upon completion to product owner
- Product owner sends all-clear to Arch-systems listserv and the desktop support team along with a link to the new client
- Archivists upgrade their own client when possible; desktop support upgrades clients for which they have tickets within a 1-2 hour window following the all-clear message. Desks behind security barriers may require a longer window.