[OPEN-ILS-GENERAL] Release notes for 2.1.0 - stub document

[bfeifarek at q.com]

Dan and Galen ++ 

Thanks for the stub document and for the thorough checklist.  I will contribute to it in the next days as I get openings in my schedule.  

For those of us who do not have commit rights to the working branch, is replying to the General mail list, or should we shift it to the Documentation mail list?   Or would it be cleaner to have a Launchpad release notes node to make the process similar to the features and bug fixes that get tracked there?

Brian

----- Original Message -----
From: "Galen Charlton" <gmc at esilibrary.com>
To: open-ils-general at list.georgialibraries.org
Sent: Monday, October 10, 2011 9:02:46 AM
Subject: Re: [OPEN-ILS-GENERAL] Release notes for 2.1.0 - stub document

Hi,

On 10/05/2011 04:27 PM, Dan Scott wrote:
> Towards that end, I have created a stub RELEASE_NOTES.txt document in
> Asciidoc format in the Evergreen "working" git repo, under the
> collab/dbs/release_notes_2_1 branch. You can see the current state of
> the source document (as of the time of me writing this email) at
> http://ur1.ca/5b69o and I've posted the HTML version at
> http://evergreen-ils.org/documentation/release/RELEASE_NOTES_2_1_0.html
>
> I would invite you to help expand this document with your suggestions,
> either by committing your changes directly to the working branch if you
> have commit privileges, or by simply sending suitable paragraphs as a
> response to this thread. Let's do this!

And to echo Dan (and to meta-echo Dan), I've started a checklist of 
things to include in the release notes here:

http://evergreen-ils.org/dokuwiki/doku.php?id=dev:release_notes_checklist

If you're looking for specific areas to contribute to, compare the 
checklist with the current state of the release notes.  In particular, 
since I know several users have been testing various pre-gold releases 
of 2.1, there's already some experience in the wild to inform the 
install and upgrade sections and to translate the descriptions of some 
of the new features to what they mean for librarians.

Of course, if you want to make suggestions or changes to the checklist 
itself, feel free - it's on the wiki.

Regards,

Galen
-- 
Galen Charlton
Director of Support and Implementation
Equinox Software, Inc. / Your Library's Guide to Open Source
email:  gmc at esilibrary.com
direct: +1 770-709-5581
cell:   +1 404-984-4366
skype:  gmcharlt
web:    http://www.esilibrary.com/
Supporting Koha and Evergreen: http://koha-community.org & 
http://evergreen-ils.org