I was definitely going to separate 1.6 and 2.0 and we are going to separate the 
branches based on version.  I was mostly wondering ff the content changes 
between 1.6.0 and 1.6.1 were drastic enough to separate.


Thanks,
Robert


________________________________________
From: [email protected] 
[[email protected]] On Behalf Of Galen 
Charlton [[email protected]]
Sent: September 15, 2010 1:26 PM
To: Documentation discussion for Evergreen software
Subject: Re: [OPEN-ILS-DOCUMENTATION] A simple sys-admin doc addition.

Hi,

On Sep 15, 2010, at 1:02 PM, Soulliere, Robert wrote:
> I did have a question as to whether we wanted to separate 1.6.0 and 1.6.1 
> into 2 versions of the documentation or keep them in the same manual  version 
> with notes regarding features specific to 1.6.1? I am not quite sure about 
> the implications of doing it either way in regards to merging changes to 
> these documents across branches in the repository.

Since, roughly speaking, the documentation for 1.6.1 would be the 1.6.0 
documentation plus a chapter on booking, keeping them together would be OK if 
it is more convenient for DIG.  However, that wouldn't work for 2.0, since 
there will be a long period of time where some libraries will be running 1.6.x 
and others 2.x, so separate versions of the manuals would be a good thing.

Of course, multiple versions can be maintained in the same Git repository using 
different branches.

Regards,

Galen
--
Galen Charlton
VP, Data Services
Equinox Software, Inc. / Your Library's Guide to Open Source
email:  [email protected]
direct: +1 352-215-7548
skype:  gmcharlt
web:    http://www.esilibrary.com/

_______________________________________________
OPEN-ILS-DOCUMENTATION mailing list
[email protected]
http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation

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.
_______________________________________________
OPEN-ILS-DOCUMENTATION mailing list
[email protected]
http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation

Reply via email to