Alexandru Popescu wrote:
I see two clear stages:
- a product that is ready from developers point of view
- a product that gets its users acceptance
An OSS project can take the same approach or not, and this is up to
its management. However, I feel that a project that would like to be
widely used cannot be labeled as released version without the user
acceptance.
I understand Don's concern about how these steps should be managed,
but I think this is not a very complex process:
- developer's ready version: beta
- (after a scheduled period during which only fixes go in if
necessary): GA.
I would love it if we actually did this. Unfortunately, we don't do the
second step, which is to have a scheduled period that allows fixes to go
in if necessary. What we actually do is freeze the code in a test
build, and put that through an undetermined period after which it may be
reassessed. If any problems are found after the build, the whole
process starts again. What this results in is a project that very, very
rarely releases a GA release because issues are always found after the
test build. If you don't believe me, look how often we put GA releases
out with Struts 1 and that was with a code base that rarely saw any
significant development/features. Imagine how long it would take us to
get out a release on a very active project...
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
