I am curious if there is an actual method or formula to setting a version number to your program.
In geel9's Source:Flash project, his version is apparently 0.001.
geel9's project is also an alpha apparently, which leads to another question:
Is there a method to determining whether or not your project is an that pre-alpha, alpha, or beta state?
MajorVersion.MinorVersion.BuildNumber I use
But no, there isn't exactly an assumed version number where you program is out of alpha / beta, except maybe 1.0
That was fast. Thanks for the info Dotmister.
How I generally see it, pre-alpha consists of tech-demos 'n stuff. Mostly snippets and technologies you wanna test before beginning with the actual project.
Alpha is the stage where you work on the project.
Beta the feature-complete project.
Release Candidate (short RC) just like the name says the as bugfree and feature-complete suspected project.
Gold is the final release. Which might not be so final if there's still bugs :P
You can also differentiate between open or closed alphas/betas/..., closed meaning that you have a selected group of people testing, or open meaning that anyone can grab and test a copy.
As for versioning, I don't think I've ever versioned stuff much.
I'd just use A(lpha)1, A(lpha)2, ... B(eta)1, B(eta)2, ... for the external releases.
Basically how I do it too. Alpha is a WIP, Beta is feature complete but not bug-"free", Release Candidate is what you consider bug-free, and you send those out for testing. You fix the bugs that come up, until no obvious bugs can be found, and then that last RC becomes your release version.
I just name my stuff "build x" or "rX" where x is the revision number of what I checked into svn :P
An entire line leading up to a release gets a name and then I just tack Alpha, Beta, or Release after that before possibly starting at Beta again for an update. I only do that if I have to do so and I have the choice, though - by myself I do rolling releases which I just stick on a repo because that's apparently how most of the module archives for Common Lisp work.
Sorry, you need to Log In to post a reply to this thread.
