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
use Perl Log In
jouke (587)
jouke
jouke@pvoice.org
http://jouke.pvoice.org/
Jouke has been programming Perl since 1997 and started using Perl to write programs to make life and communication easier for disabled people early 2001. Take a look at his website [pvoice.org] for more information.
jouke@pvoice.org
http://jouke.pvoice.org/
Jouke has been programming Perl since 1997 and started using Perl to write programs to make life and communication easier for disabled people early 2001. Take a look at his website [pvoice.org] for more information.
Wednesday August 25, 2004
08:16 AM
Version numbers
Since pVoice 2.1 came out I've been struggling with version numbers. I've now released two betas for 2.2, but if I manage to develop wat I want to, I should be calling it 3.0.
Anyway, I've just set up a mailinglist for people who are helping/want to help with pVoice development. That also includes translating pVoice and testing it. If you're interested, you can subscribe at http://opensource.pvoice.org/subscribeform.html
It's going to be a low traffic mailinglist, so I won't flood your mailbox...
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
version numbers (Score:1)
I've finally settled on just having integers -- 0 for "Initial Development", 1 for "All Initial Features Implemented", 2 for "Next Batch Of Features", etc. -- followed by the revision number from the VC repository for fine-grained versioning (usually in parentheses like "R1 (163)", but following a dot for CPAN lik