On Monday, December 16, 2002, at 09:45 AM, Henning P. Schmiedehausen wrote:
i think that there are two slight different issues here.Sam Ruby <[EMAIL PROTECTED]> writes:I believe that projects in a perpetual state of alpha are not condusive to a healthy commons.Are there plans to address this issue?The lessons to be learned here is IMHO "release early, release often". That's IMHO the main problem with many Jakarta projects.
1. components in the commons proper
by my count, there are only three components without (even alpha) releases and two more which only have alpha and beta releases. that's not a huge number. are these components (in commons-proper) the projects you were referring to, sam?
but i agree with henning that the commons proper has got a bit slack with releases. i think what's needed are more alpha and beta releases. these allow solid dependencies but don't freeze the API. maybe the charter needs to be changed to insist that every component creates an alpha release as soon as it's promoted.
2. sandbox components
IMHO this seems (to me) to be less healthy. it seems to me that there are conflicts here between the various aims/usages of the sandbox. maybe could make things clearer by categorizing the components in there.
- robert
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
