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.

use Perl

All the Perl that's Practical to Extract and Report

A simplified parseable format for Changes files More | Login | Reply

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

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Compatibility and security (Score:2)

by Juerd (1796)

I think that *incompatible changes* and *security fixes* are very important to indicate separately in a machine readable way. Just like security fixes make you install the new version asap, incompatible changes make you wait until you have tuits for updating your code. (And when they're there together, good luck.)

For these, I suggest "i" and "s".

Actually, single letters make bad identifiers. How about the following self-descriptive tags:

new
fix
doc
incompatible
license
maint
security
tests

Where changes and removal
- Re:Compatibility and security (Score:1)
  
  by Skud (28) on 2007.11.11 18:11 (#58982) Homepage Journal
  
  I agree with Juerd on all points, but most especially that using a word rather than a letter helps a lot with readability. So, what he said.
  
  --
  Kirrily "Skud" Robert perl@infotrope.net http://infotrope.net/
  
  Reply to This
  
  Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.