[OPEN-ILS-DEV] Evergreen upgrade instructions for 2.3

[Soulliere, Robert]

Hi,

I updated the upgrading instruction for 2.3.1.  I tested on a server and it seemed to go well.  I wonder if could get someone to double check the steps at?

http://docs.evergreen-ils.org/2.3/_upgrading_the_evergreen_server.html

Dan, you mentioned working on it a few days ago. I wasn't sure if you meant changing reference from 2.3.0 to 2.3.1  or if you needed to make bigger changes.

At any  rate, I made a few changes and would like some testing and perhaps linking form the downloads page if it passes the tests and looks ready.

I made changes in master and cherry picked into rel_2_3 this time.

Thanks,
Robert

-----Original Message-----
From: open-ils-dev-bounces at list.georgialibraries.org [mailto:open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of Dan Scott
Sent: Friday, November 09, 2012 12:11 AM
To: Evergreen Development Discussion List
Subject: Re: [OPEN-ILS-DEV] Evergreen upgrade instructions for 2.3

On Wed, Oct 03, 2012 at 02:26:36PM -0400, Soulliere, Robert wrote:
> Hi All,
>
> I updated the upgrade instructions to reflect the 2.3.0 version of Evergreen.
> http://docs.evergreen-ils.org/2.3/_upgrade_the_evergreen_code.html
>
> I wonder if I could get someone to double check the documentation?
> Then, add a link from the downloads page, if it passes the test?

Hi Robert:

I was going to make a few tweaks to those upgrade docs for 2.3.1 but it looks like the version of docs/installation/server_upgrade.txt in master is for 2.3-beta1; I guess the commit for the 2.3.0 instructions only got into rel_2_3.  I'll push your commit into master and hopefully have some time to work on it tomorrow.

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.