Hi,

On Sun, Sep 22, 2013 at 10:55 AM, Mathieu Saby <mathieu.saby@univ-rennes2.fr> wrote:

So, when it is done, so you think we could some day (for 3.14 ? 3.16?) get rid of Zebra GRS1 ? It could make simple further improvements.
For example, I would like to make a page for configuring zebra indexes from staff interface. I think it can be done by parsing bib1, ccl.properties and xml DOM conf files. But I don't want to parse record.abs...

I don't think there's anything GRS-1 does that DOM cannot do.  It's too late by far to consider removing GRS-1 support for 3.14, but it is not too late to make a deprecation announcement with the release of 3.14 and plan on having it be removed in the release after 3.14 (or the release after that).

Consequently, I hereby open a straw poll for folks to indicate whether or not they think that announcing a deprecation is sensible.

Regards,

Galen

--

Galen Charlton

Manager of Implementation

Equinox Software, Inc. / The Open Source Experts

email:  gmc@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

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/