[EMAIL PROTECTED] wrote:
> The current rule is that a jakarta project can "sponsor" a component in
> the sandbox/agora. The components in the sandbox/agora are developed by
> jakarta commiters, and may included in multiple jakarta projects - so
> probably they have a higher quality standard and more review than
> most components that will be developed and maintained by 3-4 library
> developers.
How does the code get out of the sandbox and into the multiple products?
Before when we talked about it being released as part of the product, I
thought that meant the code would be placed in the product's CVS, and
made part of the product's distribution. That's what I meant by
sponsored.
For the Commons, each package would have a separate root branch, with
it's own build, along with ready-to-run JARs, that could be downloaded
via the catalog.
Is that what you planned to do with Agora?
I believe that there has to be a clear, documented vote before we can
release the code under the Apache brand.
So after getting the build for Tomcat, do I then have to get the build
for the entire sandbox, or would the tagged branch be available
separately?
If the tagged branch is available separately, then can one or more
of the subprojects vote specifically on that branch before it is
released to the public?
Part of the problem is that I don't grasp the mechanics of Agora.
-Ted.
