Changes between Version 2 and Version 3 of BluePrintUpgrades

Timestamp:

02/13/16 12:58:40 (9 years ago)

Author:

Pat Tressel

Comment:

--

BluePrintUpgrades

@@ -1 +1 @@
 = Upgrades !BluePrint =
+
+== Goal ==
 
 '''Target user''': System Administrator of a production system (or the IT operations manager)
 
-'''Goal''': Make operations a big fan of our software - make it more stable, robust and scalable. Make it very easy for them to upgrade. 
+'''Goal''': This is one part of making operations a big fan of our software: Make it very easy for them to upgrade. 
 
-Features:
-    * Nice upgrade experience (automatic updates?) 
-    * Stability, production ready and tested 
-    * Certified on different hardware/software - painless deployment (so we need a nice testing/qa process for running on different set ups) 
-    * Features based on actual user research of useful tools to run their service better - both the system and supporting their users. 
+== Upgrade Issues ==
 
-(Taken from http://projects.opengeo.org/suite/wiki/Roadmap#MilestoneOperations)
+The current process is manual: UserGuidelines/Admin/Upgrade
 
-Current Process:
- * UserGuidelines/Admin/Upgrade
-Plans:
- * BluePrintlivecdinstaller#OnlineProfile
+For other software, people are used to automatic upgrades.  Even the (very complex) Windows operating system auto-upgrades.
+What can make an Eden upgrade problematic?  There are two types of visible changes:
+
+* Structural changes: These are changes that affect data structure and file layout.
+  * Database schema changes
+  * Directory structure changes
+  * Configuration process and parameter changes
+* Functional changes: These are changes that would alter the site behavior or layout, in non-trivial ways.
+  This would affect users, and might require retraining.
+
+
 
 ----