Skip Menu |

This queue is for tickets about the CPAN-Changes CPAN distribution.

Report information
The Basics
Id: 67527
Status: resolved
Priority: 0/
Queue: CPAN-Changes
People
Owner: Nobody in particular
Requestors: DOHERTY [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Sat Apr 16 22:20:01 2011 DOHERTY [...] cpan.org - Ticket created
Subject: Popularity of 'Changes' doesn't mean it is the best filename choice
Hello, While I appreciate the effort you made in measuring the popularity of certain filenames for the changelog, simply choosing the most common one is not the best way to make that decision. Was this discussed with anyone else prior to declaring it to be so? Since the other metadata files tend to be in caps (META.{yml,json}, MANIFEST, INSTALL, README...), I think the changelog should be in 'CHANGES'.
  Wed Apr 20 10:32:08 2011 bricas [...] cpan.org - Status changed from 'new' to 'open'
  Tue May 03 12:46:26 2011 bricas [...] cpan.org - Correspondence added
Sorry for the delay in my response. I believe your question to be an entirely valid one. I did, in fact, consult with some CPAN authors regarding the choice of filename for a changelog. The consensus was that, in order to gain the most amount of buy-in from CPAN authors, you should standardise on existing conventions. I've tried my best to apply this notion to every aspect of CPAN::Changes; from the filename to the details of each release in a changelog. The overwhelming evidence is that about 80% of existing distributions use "Changes" [1]. It is much easier to use that filename, then go against the grain and ask them all to change to something else. Whilst I understand see your point of view, I don't believe that naming scheme would gain wide adoption. Thanks for your time, -Brian [1] http://blog.alternation.net/re-changes-filenames
  Tue May 03 12:46:28 2011 bricas [...] cpan.org - Status changed from 'open' to 'resolved'