Josh,
I participated in a previous thread on this topic, but I couldn't find
it (maybe it was blog comments?) From memory, I think we concluded
that, no, there was no formal spec and that it would be too painful to
build one broad enough for everyone's taste. So, we dropped the
idea. My own ad-hoc syntax looks like this example:
http://cpansearch.perl.org/src/CDOLAN/Fuse-PDF-0.09/Changes
In retrospect, I may have gotten a little carried away with too much
detail... For my own syntax, I wrote an author unit test that checks
that all versions have a summary and a release date. I never got
around to writing the test that ensured the .pm's current version
number had an entry in the changelog.
Chris
> Last year I started seeing change logs in perl modules that looked
> more YAMLish. Is there any spec out there on this? I'm currently just
[quoted text clipped - 14 lines]
>
> Josh
Kevin Ryde - 30 Jun 2009 01:49 GMT
> I never got around to writing the test that ensured the .pm's current
> version number had an entry in the changelog.
Maybe Test::CheckChanges, though I found myself putting an empty entry
to satisfy it for making a trial dist, which defeats the purpose of a
check of course. (Have to flag somehow when doing a prospective release
as against a work-in-progress check build.)
Curtis Jewell - 30 Jun 2009 15:51 GMT
use $ENV{RELEASE_TESTING} as that flag?
(That's what's done to hide the l..o..n..g.. tests in Perl::Dist and
Perl::Dist::WiX that take hours, as opposed to seconds, to complete, so
that I only do those tests when I'm ready to release.)
--Curtis
> > I never got around to writing the test that ensured the .pm's current
> > version number had an entry in the changelog.
[quoted text clipped - 3 lines]
> check of course. (Have to flag somehow when doing a prospective release
> as against a work-in-progress check build.)
--
Curtis Jewell
swordsman@csjewell.fastmail.us
%DCL-E-MEM-BAD, bad memory
-VMS-F-PDGERS, pudding between the ears
[I use PC-Alpine, which deliberately does not display colors and pictures in HTML mail]
Shlomi Fish - 01 Jul 2009 09:56 GMT
> Josh,
>
> I participated in a previous thread on this topic, but I couldn't find
> it (maybe it was blog comments?)
Maybe you're referring to:
http://use.perl.org/~hex/journal/34864
?
Regards,
Shlomi Fish
> From memory, I think we concluded
> that, no, there was no formal spec and that it would be too painful to
[quoted text clipped - 29 lines]
> >
> > Josh

Signature
-----------------------------------------------------------------
Shlomi Fish http://www.shlomifish.org/
http://www.shlomifish.org/humour/ways_to_do_it.html
God gave us two eyes and ten fingers so we will type five times as much as we
read.
> Last year I started seeing change logs in perl modules that looked
> more YAMLish. Is there any spec out there on this? I'm currently just
> copying input from `git log --pretty=oneline' into my Changes file and
> as of this moment, including the git repo URL.
I'm not aware of any spec. There's Module::Changes, which I have poked at
briefly but not used for anything serious.
hdp.
> Last year I started seeing change logs in perl modules that looked
> more YAMLish. Is there any spec out there on this? I'm currently just
> copying input from `git log --pretty=oneline' into my Changes file and
> as of this moment, including the git repo URL.
>
> Is there any external standard or pattern I can conform to?
Thanks!