[EMAIL PROTECTED] wrote:
> There are 2 issues:
> 1. A project should be able to share some code/components. I don't see
> myself using or participating in a library that is not open to all
> jakarta projects.
>> Committers join the library subproject in the same way they are entered to any
>Jakarta subproject.
This is what most people want, and so this is what will happen. Everyone
has heard the arguments, and made their decision. We voted, and it's
time to move on. If this is a showstopper for you, then so be it. No one
wants you to do anything you don't want to do.
> 2.
> If a project is preparing for a release - it should be sure that it have
> stable components to use ( even if he's not involved in writing the
> components ).
>> Each package has its own status file, release schedule, version number, QA tests,
>documentation, mailing list, and bug category.
Personally, I would build against the latest stable release of the
package, unless a feature I needed had been added to a nightly build. If
a later nightly build breaks my code, I can always roll back to the
latest one that didn't.
-T.
