Really up to the person at the wheel - OpenOffice just used build numbers until they decided it was a release candidate, Mozilla used the 0.xx system until they had the functionality they originally aimed to have. Our (wonderful) helpdesk (http://helpdesk.centralmanclc.com) is using version numbering similar to Mozilla: v1.0 will be the first full release - by this we would mean it has everything fully (as far as we can tell) functional that we initially intended it would have. Any successive versions will have either additional functionality or (highly unlikely, of course ;-) ) bug fixes.* Major functionality additions add a .1 to the release, minor additions and bug fixes add a 0.01. The helpdesk has been in "live" use since 0.4 (about a month ago, now 0.7) without any significant problems from either a user or data loss perspective. * Minor caveat: so much input from people from beyond the sponsoring organisation that v1.0 will now have considerably more functionality than originally intended... Cheers Chris -----Original Message----- From: Matt Johnson To: SuSe Sent: 6/4/03 5:00 PM Subject: [suse-linux-uk-schools] Numbering my applications Hi folks, I've googled this and pulled nothing. So, I'm writing my first 'application' in PHP. The only tenuous link to keep this 'on topic' is that I'm writing it on SuSE 8.2/Apache/MySQL/PHP. Could someone point me to what state my app should be in to constitute 'Alpha', then 'Beta', then 'version 1'. And equally, how do I 'number' it accurately to enable others to know where it's at on it's road to version 1? And as for 'release candidates'... Is there a universal system at work? If so, where's it at? Or is it up to the person at the wheel? Thanks for any pointers. All a bit new :) -- Matt Johnson __________________________________________________ Yahoo! Plus - For a better Internet experience http://uk.promotions.yahoo.com/yplus/yoffer.html -- To unsubscribe, e-mail: suse-linux-uk-schools-unsubscribe@suse.com For additional commands, e-mail: suse-linux-uk-schools-help@suse.com
participants (1)
-
Chris Puttick