[OPEN-ILS-DEV] #help Evergreen 2.2 Release

[Soulliere, Robert]

Hi Anoop,

Does the release-notes-writer role basically take what is in the raw release notes from the master file as added by developers here:
http://git.evergreen-ils.org/?p=Evergreen.git;a=blob_plain;f=docs/RELEASE_NOTES_2_2.txt;hb=master

and get them into the official docs such as here?:
http://docs.evergreen-ils.org/2.2/_release_notes.html

If so, perhaps I can help with that and take on that role? Can we just use one source for that in the official docs or do we need to add a wiki page as well?

Also note that we have upgrade instruction in the official docs here:
http://docs.evergreen-ils.org/2.2/_upgrading_the_evergreen_server.html
-- this is based on the alpha release, but if you give me a few days heads up before the official release will be released, I could get those updated to reflect the official tarball version. It might also be good to have a few folks review the upgrade instructions chapter as well.

In general I think DIG has more documentation ready to go for 2.2 than we did for past releases.
See:
http://docs.evergreen-ils.org/2.2/

Thanks,
Robert

Robert Soulliere, BA (Hons), MLIS
Systems Librarian
Mohawk College Library
robert.soulliere at mohawkcollege.ca
Telephone: 905 575 1212 x3936
Fax: 905 575 2011
________________________________________
From: open-ils-dev-bounces at list.georgialibraries.org [open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of Anoop Atre [anoop.atre at mnsu.edu]
Sent: February 27, 2012 5:18 PM
To: Evergreen Development Discussion List
Subject: [OPEN-ILS-DEV] #help Evergreen 2.2 Release

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

This E-mail contains privileged and confidential information intended
only for the individual or entity named in the message.  If the reader
of this message is not the intended recipient, or the agent responsible
to deliver it to the intended recipient, you are hereby notified that
any review, dissemination, distribution or copying of this communication
is prohibited.  If this communication was received in error, please
notify the sender by reply E-mail immediately, and delete and destroy
the original message.