On Thu, Dec 16, 2004 at 05:10:45PM -0600, Bryan Baldus wrote: > I hope to have time to work on this this weekend. The only changes I plan to > make to the current version are the DATA fixes described before (adding > 001-008 and correcting the valid/obsolete indicator values). I've downloaded > the most recent tag list, with update 4 (Oct. 2003). I planned on cleaning > that up and adding it to the DATA section for the first stand-alone release. > > Other than the readme (currently empty), is there anything else that would > prevent the current files in CVS from being released as the first CPAN > version?
Before you update anything how about we do a release to CPAN of what we have right now? I've populated the README and changed the version to 1.39 to start with. > I haven't really looked around in my CVS client's settings--do most > have a way of telling the server what version to set/how much to > increment the version when a file is added/committed? The version is defined in the lib/MARC/Lint.pm file. Before releasing it this normally needs to be updated. It's often a good idea to 'tag' the project when you've got a release version. This way you can roll back to a previous version when necessary. Most CVS clients will support tagging. I tagged 1.39 as v1-39. > I would definitely need help in producing a release for CPAN. My SSH/CVS > clients are only available at home, which is an unreliable dial-up > connection, so I rarely log on there. My AIM client hasn't gotten much use > in the past few years, but perhaps now would be a good time to see if it > still runs. I think my username, if it still exists, is similar to my CPAN > e-mail address. Ok, in that case I'll upload 1.39 myself and make you a maintainer. This way the MARC::Record distribution can reference MARC::Lint if necessary, and you'll have a baseline version to move forward from. //Ed
