mikery++
-bill
On 1/25/07, Mike Rylander <[EMAIL PROTECTED]> wrote:
OK, folks, MARC::Record 2.0.0 is officially out.
http://search.cpan.org/~mikery/MARC-Record-2.0.0/lib/MARC/Record.pm
Give it a go, and let me know if you see anything broken. Sorry for the
delay!
-miker
On 1/19/07, Paul
OK, folks, MARC::Record 2.0.0 is officially out.
http://search.cpan.org/~mikery/MARC-Record-2.0.0/lib/MARC/Record.pm
Give it a go, and let me know if you see anything broken. Sorry for the delay!
-miker
On 1/19/07, Paul POULAIN <[EMAIL PROTECTED]> wrote:
Mike Rylander a écrit :
> So it is w
Mike Rylander a écrit :
So it is written, so it shall be done.
It doesn't seem too off the mark (heh...) anyway, since the name
MARC::Record2 (and variants) has been bandied about quietly in the
past.
Thoughts/comments/sharp-sticks-in-the-eye?
+1 for kicking version number to 2.0.0
- for u
On 1/18/07, Anne Highsmith <[EMAIL PROTECTED]> wrote:
There's a MARC::Record version with Unicode support that Ed Summers
developed for us and gave the version number 2.0. We've been using it
for quite a while. Might the latest, greatest need a 2.0.1 or something
higher, perhaps?
I was unaware
There's a MARC::Record version with Unicode support that Ed Summers
developed for us and gave the version number 2.0. We've been using it
for quite a while. Might the latest, greatest need a 2.0.1 or something
higher, perhaps?
Anne L. Highsmith
Consortia Systems Coordinator
5000 TAMU
Evans Library
On 1/18/07, Cory Snavely <[EMAIL PROTECTED]> wrote:
As an administrator who doesn't use the module but is waiting for it to
be packaged on CPAN to more easily provide updates to users, I have to
say this is all great.
I see no strong reason to bump the version to 2.0.0, but I have no
objection e
As an administrator who doesn't use the module but is waiting for it to
be packaged on CPAN to more easily provide updates to users, I have to
say this is all great.
I see no strong reason to bump the version to 2.0.0, but I have no
objection either, especially if that feels appropriate to those w
So it is written, so it shall be done.
I think, because of the number and size of the changes involved, it
would be good to stamp the next version of MARC::Record as 2.0.0.
There's a good bit of stuff that hasn't been very widely tested,
though I know Evergreen and Koha use it on a daily basis, a