This is a call for volunteers to assist in the 2.2 release of Evergreen
and go over the release checklist. If you are willing to assist please
mail back or update the wiki:
http://www.evergreen-ils.org/dokuwiki/doku.php?id=dev:evergreen:release_checklist
Dan Scott has recently updated the release checklist page but it needs
folks to look over and review roles/suggest possible new ones or changes
in workflow (DIG for documentation sign-off? Do we need a client
packager anymore?).
He specifically mentions the following things that need to be discussed:
- who actually will create the script (I lamely said evergreen-dev which
leaves it pretty wide open)
- naming conventions for the point-to-point upgrade scripts to avoid any
ambiguity
- expectations about what data should be upgraded and what should not be
touched (for example, permissions and permission groups)
- how to notify users about any outstanding manual steps that may need
to be taken to complete the database schema upgrade
Your comments & ideas are much appreciated.
Cheers
--
Anoop Atre
IS Developer & Integrator, PALS
PH: 507.389.5060
OF: 3022 Memorial Library (Office-ML 3022)
--
"Mit der Dummheit kämpfen Götter selbst vergebens"
~ Johann Christoph Friedrich von Schiller
