Skip Menu |

This queue is for tickets about the version CPAN distribution.

Report information
The Basics
Id: 116341
Status: rejected
Priority: 0/
Queue: version
People
Owner: Nobody in particular
Requestors: dolmen [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Important
Broken in: 0.9917
Fixed in: (no value)

History Show all quoted text
  Wed Jul 20 11:17:38 2016 dolmen [...] cpan.org - Ticket created
Subject: 'Changes' file is unreadable by humans
The 'Changes' file should be readable by humans.

In its current state (release 0.9917) it contains just garbage that seems do come from a VCS log. This is absolutely useless for a human interested in knowing what changed release by release. It could be removed.

What I would like in the Changes file is what I see in the README file.
https://metacpan.org/source/JPEACOCK/version-0.9917/README


-- 
Olivier Mengué - http://perlresume.org/DOLMEN
  Fri Jul 22 11:58:47 2016 jpeacock [...] cpan.org - Correspondence added
The Changes file is indeed based on the commit messages from the repository. That's all it is and it has been that way forever. Any important changes are called out in the README, as you noted. I'm sorry you don't find it useful; I'll try to add more useful commit messages in the future. John
  Fri Jul 22 11:58:48 2016 The RT System itself - Status changed from 'new' to 'open'
  Fri Jul 22 11:58:48 2016 jpeacock [...] cpan.org - Status changed from 'open' to 'rejected'
  Wed Aug 03 19:11:31 2016 MAUKE [...] cpan.org - Correspondence added
On Fri Jul 22 11:58:47 2016, JPEACOCK wrote: Show quoted text
> The Changes file is indeed based on the commit messages from the > repository. That's all it is and it has been that way forever. Any > important changes are called out in the README, as you noted. I'm > sorry you don't find it useful; I'll try to add more useful commit > messages in the future.
Why? I mean, what's the point of collecting commit messages and sticking them into a file in the distribution?