Bug #40752 for XML-DTD: Version mismatch between module and tarball

Fri Nov 07 15:31:06 2008 admiral.grinder [...] gmail.com - Ticket created

Subject:

Version mismatch between module and tarball

There is a mismatch between what the module says it is and the tarball that delivers. Module and docs currently say 0.03 and the tarball is currently 0.07

Mon Nov 10 10:08:28 2008 admiral.grinder [...] gmail.com - Correspondence added

From:

admiral.grinder [...] gmail.com

Email from brendt: Hi, Show quoted text

> Queue: XML-DTD > [...] > There is a mismatch between what the module says it is and the tarball > that delivers. Module and docs currently say 0.03 and the tarball is > currently 0.07

I consider the tarball (and Makefile.PL) version to be a release version, distinct from the versions of individual modules contained therein. You might notice that different modules within the distribution have different version numbers - if a new release only contains modifications to some of the modules, I only increment the version numbers of the modified modules and the release version number. I realize this might be a little unusual, but haven't been able to find any Perl guidelines according to which it's actually considered erroneous. Nevertheless, if you can point me to some relevant guidelines, or make a good argument why I should, I'll fix it. Regards, Brendt

Mon Nov 10 10:09:05 2008 admiral.grinder [...] gmail.com - Correspondence added

From:

admiral.grinder [...] gmail.com

My argument is consistency with the rest of CPAN and ease of use on your users.. In the past week I have had to download 70 modules in support of our application when we changed our perl distribution. Out of the 70, only XML::DTD and Workflow have the mis-matched version numbers. When users download XML::DTD, they are not thinking what sub modules are included with it since they are using 'XML::DTD' and not 'XML::DTD::something'. So when I looked up the XML::DTD in our bundle and saw that it was 0.03 I went to download 0.03 and not 0.07. This is a problem because you now have 4(?) releases of XML::DTD that are labeled 0.30 with the only way to tell them apart is to dive into each sub module (17 of them according to cpan) and look up the versions of them (I shouldn't have to argue how much a pain that is). There are no problems keeping different versions of the submodules in the module, but when you make a change to one of them, you are making a change to XML::DTD as a whole, thus its version needs to change to reflect the update. Now we just happen to be in control of what modules we install, but if we are on a shared system how are we to know what version of XML::DTD the admin has on the box (if even they know)? I have forwarded your reponse to my 12 coworkers and they agree with me that the version number to XML::DTD needs to reflect changes to the module as a whole. How you want deal with that is fine, be it a point release or what not.

Tue Nov 11 16:06:46 2008 wohl [...] cpan.org - Status changed from 'new' to 'resolved'

Tue Nov 11 16:07:55 2008 wohl [...] cpan.org - Correspondence added

Fixed in 0.08.

Tue Nov 11 16:08:22 2008 The RT System itself - Status changed from 'resolved' to 'open'

Tue Nov 11 16:09:01 2008 wohl [...] cpan.org - Status changed from 'open' to 'resolved'

Wed Nov 12 09:25:38 2008 admiral.grinder [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #40752] Version mismatch between module and tarball
Date:	Wed, 12 Nov 2008 14:25:27 +0000
To:	bug-XML-DTD [...] rt.cpan.org
From:	"Brian Pugh" <admiral.grinder [...] gmail.com>

Thanks 2008/11/11 Brendt Wohlberg via RT <bug-XML-DTD@rt.cpan.org> Show quoted text

> <URL: http://rt.cpan.org/Ticket/Display.html?id=40752 > > > Fixed in 0.08. > >

Wed Nov 12 09:25:41 2008 The RT System itself - Status changed from 'resolved' to 'open'

Wed Nov 12 10:54:45 2008 wohl [...] cpan.org - Fixed in 0.08 added

Wed Nov 12 10:54:57 2008 wohl [...] cpan.org - Status changed from 'open' to 'resolved'