Bug #94686 for TermReadKey: "Changes" file is empty

Sun Apr 13 10:17:07 2014 dolmen [...] cpan.org - Ticket created

Subject:

"Changes" file is empty

The 'Changes' file is empty. A file with meaningful content would be helpful for users of the distribution. See CPAN::Changes::Spec for a common format for 'Changes'. https://metacpan.org/pod/distribution/CPAN-Changes/lib/CPAN/Changes/Spec.pod -- Olivier Mengué - http://perlresume.org/DOLMEN

Mon Apr 14 13:28:03 2014 jonathan.stowe [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #94686] "Changes" file is empty
Date:	Mon, 14 Apr 2014 18:27:50 +0100
To:	bug-TermReadKey [...] rt.cpan.org
From:	Jonathan Stowe <jonathan.stowe [...] gmail.com>

Cheers, I'll try and put something in the Changes file for the next release. On Sun, 2014-04-13 at 10:17 -0400, Olivier Mengué via RT wrote: Show quoted text

> Sun Apr 13 10:17:07 2014: Request 94686 was acted upon. > Transaction: Ticket created by DOLMEN > Queue: TermReadKey > Subject: "Changes" file is empty > Broken in: 2.31 > Severity: (no value) > Owner: Nobody > Requestors: dolmen@cpan.org > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=94686 > > > > The 'Changes' file is empty. A file with meaningful content would be helpful for users of the distribution. > See CPAN::Changes::Spec for a common format for 'Changes'. > https://metacpan.org/pod/distribution/CPAN-Changes/lib/CPAN/Changes/Spec.pod >

Mon Apr 14 13:28:04 2014 The RT System itself - Status changed from 'new' to 'open'

Fri Jun 05 14:50:33 2015 jns [...] gellyfish.co.uk - Correspondence added

Hi, Since moving this to github I have been using git2cl to generate the Changes file, this would have gone out in the previous release.

Fri Jun 05 14:50:39 2015 jns [...] gellyfish.co.uk - Status changed from 'open' to 'resolved'

Fri Jun 05 14:50:40 2015 jns [...] gellyfish.co.uk - Fixed in 2.32 added

Tue Jun 09 08:29:35 2015 dolmen [...] cpan.org - Correspondence added

Le 2015-06-05 20:50:33, JSTOWE a écrit :
Show quoted text

> Hi,
> Since moving this to github I have been using git2cl to generate the
> Changes file, this would have gone out in the previous release.

Oh, no! This is awful.

From a user point of view, a git log is completely unreadable when all I want to know is what changed from the last release or for the last 5 releases since my last upgrade. I don't need to know every minor typo fixed in the README or changes that occured in the .gitignore (that is not even in the distribution).

--
Olivier Mengué - http://perlresume.org/DOLMEN - https://gratipay.com/dolmen/

Tue Jun 09 08:29:36 2015 dolmen [...] cpan.org - Status changed from 'resolved' to 'open'

Tue Jun 09 09:17:11 2015 jonathan.stowe [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #94686] "Changes" file is empty
Date:	Tue, 09 Jun 2015 14:16:45 +0100
To:	bug-TermReadKey [...] rt.cpan.org
From:	Jonathan Stowe <jonathan.stowe [...] gmail.com>

I'm sorry this is awful, but as a developer I don't have time to do please everybody. I fix bugs, I release them. I'll be sure to bear your comments in mind when I next make a release. I'd ask for your money back if I were you. On Tue, 2015-06-09 at 08:29 -0400, Olivier Mengué via RT wrote: Show quoted text

> Queue: TermReadKey > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=94686 > > > Le 2015-06-05 20:50:33, JSTOWE a écrit :

> > Hi, > > Since moving this to github I have been using git2cl to generate the > > Changes file, this would have gone out in the previous release.

> > Oh, no! This is awful. > > From a user point of view, a git log is completely unreadable when all I want > to know is what changed from the last release or for the last 5 releases since > my last upgrade. I don't need to know every minor typo fixed in the README or > changes that occured in the .gitignore (that is not even in the distribution). > > -- > Olivier Mengué - http://perlresume.org/DOLMEN - https://gratipay.com/dolmen/ >

Sun Dec 04 15:22:46 2016 jns [...] gellyfish.co.uk - Correspondence added

fixed

Sun Dec 04 15:22:47 2016 jns [...] gellyfish.co.uk - Status changed from 'open' to 'resolved'

Sun Dec 04 15:22:52 2016 jns [...] gellyfish.co.uk - Fixed in 2.37 added

Sun Dec 04 15:22:52 2016 jns [...] gellyfish.co.uk - Fixed in 2.32 deleted