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...
version numbers
mdxi on 2004-08-26T14:00:15
There are so many standards for how version numbers work and what version numbers mean that they have become completely worthless except as an indicator that THIS version comes after THAT version.
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 like "1.163").
