On Mon Sep 03 12:53:27 2012, TURNSTEP wrote:
Show quoted text> Please reconsider the decision to truncate the CHANGES file. In the big
> scheme of things, a large text file in the distro is not that big of a
> deal as far as saving space. Being able to quickly grep through it, and
> being able to quickly see when a version was released (as CPAN offers not
> version pulldown list) is very valuable. Also, finding the complete
> Changes list on the website is not easy. A pointer to the exact place in
> both the README and at the bottom of the CHANGES would be nice.
I've added pointers to three online commit browsers in README and POE's documentation. The right URLs aren't readily available
to the tools I use to generate CHANGES. That's kind of sad because a link at the start and end of CHANGES would be ideal.
https://github.com/rcaputo/poe/commit/d8eec5291a94ad006e4f98d43db11a7d1821627b
https://gitorious.org/poe/poe/commit/d8eec5291a94ad006e4f98d43db11a7d1821627b
http://poe.git.sourceforge.net/git/gitweb.cgi?p=poe/poe;a=commitdiff;h=d8eec5291a94ad006e4f98d43db11a7d1821627b
I've also documented three online browsers at
http://poe.perl.org/?POE_Changes ... and I've deprecated the outdated, hand-
curated log there. This should help people find canonical information in the future.
I think the current year-long backlog serves most people well. CPAN tools hide the CHANGES file well enough that few people
give it a thought at all. Even fewer need the full 14-year history. Most people care about the changes since their last upgrade,
not ones since before the turn of the millennium or century.
