Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Tagging CPAN changes 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • I'd like an RSS feed (or whatnot) that keeps me up to date on changes to modules on my watchlist (likely, modules I have installed or I have as a prerequisite to my releases), so a machine parser for Changes files is something I'm interested in. I'm definitively in the "free format text file" camp. I'm not really against POD, but I'm against human-unreadable formats like RDF, because IMO the Changes file is still mostly for humans to consume and mostly written by humans too. At least my releases "should" be

    • So maybe the combination of these:

      Having a new site to tag each release of CPAN modules. The app by default automatically runs some ad-hoc regular expressions to extract changes like /API change/ or /security fix/ from Changes file, and display these tags as "machine parsed tags", probably in a gray color.

      The site also works with PAUSE/BitCard authentication so anyone with these IDs can tag releases. In that case we display the tag as "human tags" in a black color.

      Finally, if the user is authenticated as an author of the module, and tag them or approve the existent machine/human tags, then the tag is now "author tag" and be displayed in either bold or red.

      There should also be a greasemonkey script so you can tag directly on search.cpan.org release pages.

      Sounds like an interesting project for a hackathon :)
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.