From: open-ils-dev-boun...@list.georgialibraries.org
[open-ils-dev-boun...@list.georgialibraries.org] On Behalf Of Dan Scott
[d...@coffeecode.net]
Sent: April 5, 2012 2:56 PM
To: Evergreen Development Discussion List
Subject: Re: [OPEN-ILS-DEV] #help Evergreen 2.2 Release
Hi Robert:
I
On Mon, Apr 9, 2012 at 10:48 AM, Soulliere, Robert
robert.soulli...@mohawkcollege.ca wrote:
Hi Dan,
I agree with your proposals for more single sourcing and providing the docs
in the tarball. Our switch to AsciiDoc makes this more viable given the
usability of AsciiDoc in its raw form
Hi Robert:
I apologize, I was supposed to respond to this weeks ago.
On Tue, Feb 28, 2012 at 2:01 PM, Soulliere, Robert
robert.soulli...@mohawkcollege.ca wrote:
Hi Anoop,
Does the release-notes-writer role basically take what is in the raw release
notes from the master file as added by
Hi DIG!
On Thu, Apr 5, 2012 at 2:56 PM, Dan Scott d...@coffeecode.net wrote:
On Tue, Feb 28, 2012 at 2:01 PM, Soulliere, Robert
robert.soulli...@mohawkcollege.ca wrote:
snip
Also note that we have upgrade instruction in the official docs here:
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
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