Leo:
The subject of this message starts with [PMC:VOTE], however, I don't see anything to vote on. I don't see a release manager, a release plan, or even a release candidate. However, I did see a generic statement suggesting Avalon adopt the principal of releasing undocumented code. Is that the subject of the vote?
I hope not! Lets be clear about a few things - lowering the quality criteria for a release for Cocoon will not help Cocoon and it will not help Avalon. The lack of documentation simply reflects a lack of sufficient interest relative to the code. IMO the more import question is what we should be doing to address the viability of the code in question. Is there interests within the Avalon community in maintaining the code or not. The answer to this will be different for the individual packages.
Before considering a release - I would suggest that everyone consider the following questions:
(a) is the package relevant to Avalon
(b) is the Avalon dev community ready/willing/able to
support the packageCheers, Stephen.
Leo Simons wrote:
Hi gang!
Cocoon (arguably one of the biggest and most important "clients" for avalon) is using CVS drops of these projects:
excalibur-component excalibur-sourceresolve excalibur-store excalibur-xmlutil fortress-container fortress-tools excalibur-logger
This is an undesirable situation.
Previously, release of some of these components was blocked because of a lack of documentation. The net result is that there is still no documentation, cocoon is using custom-built packages, and many cocoon people don't feel like coming near avalon because there won't be much oppurtunity to benefit from the work they do here (which is, simply put, not very likely to be on documentation).
That's also an undesirable situation.
So lets loosen those documentation requirements a little.
Proposal: if working and thoroughly tested (with verifiable results of course) versions of the packages mentioned above are produced, lets agree to release them even if their documentation may not be exactly what we would like it to be.
I think the only alternative is to let these packages die a slow and painful death. We'll lose one of our biggest clients.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
