stages of distribution
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.
In particular, I'm referring to the different stages of release.
Such as prototype, alpha, beta, stable, unstable, any others you can
think of. And any other stages you can think of, like milestones, or
branches, compact, full, etc..
I guess this has alot to do with revision methods, and project planning.
Both are topics that I think should also be discussed.
Being a community consisting mainly of hobbyist and novice programmers,
I think alot of us have either had to learn the hard way, and that
usually entails an incomplete understanding, or else being novice, have
never been properly exposed to these concepts.
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 Bensler
Code is Alchemy
|
Not Categorized, Please Help
|
|
