OpenEuphoria

Re: stages of distribution

• Posted by cklester <cklester at yahoo.com> Dec 23, 2004
• 484 views

Chris Bensler wrote:
> 
> I figure this is a good topic for FAQ material, and to clarify for alot
> of people what steps are normally (or should be) taken in the course of
> developing and then distributing a new software product.

I'm very interested in this topic as well, not just for my personal
projects, but for corporate projects. I know that someday my code will
be passed on to the next generation of coders, and I'd like to have
some organized methodology to tracking code releases. Right now I just
use the date of release as the primary indicator, then a subsequent
integer for release number. I rarely have releases on the same day, but
sometimes I do! :/

> To start with, what is the purpose of alpha versus beta versus final
> releases?
> 
> When should a project move from development to alpha?
> Is it ok to have alpha revisions?
> When should a project move from alpha to beta?
> Is it ok to have beta revisions?
> When should a project move from beta to final?
> Is it ok to have final revisions?

Chris, check out this link: http://en.wikipedia.org/wiki/Alpha_version

Might be the answer to all our questions. :)

-=ck
"Programming in a state of EUPHORIA."
http://www.cklester.com/euphoria/