[EMAIL PROTECTED] wrote:

> > Ted Husted wrote:
> > >
> > > How about a commons-general list and a combined user/dev list for each
> > > package?
> > >
> > > jakarta-commons-general
> > > jakarta-commons-DBCP
> > > jakarta-commons-digester
>
> I would say -1 on separate CVS, +0 on separate dev/user/announce list,
> maybe later we can split dev ( or fork the most active components in
> separate lists ).
>
> I don't mind a common mailing list that much, but I'm very much
> against separate CVS - I hope we'll end up with
> a significant number of components, many of them duplicated and with
> inter-dependencies. I would like to have a single CVS tree to worry about,
> the jakarta-commons ( I'm talking as a library user ).
>
> Why not having a single CVS tree, with separate top-level dirs ?
> This seems to work fine in taglibs and catalina.
>
> I agree, for agora/sandbox we need a separate CVS ( given the access
> control ).
>

+1 ... use common CVS trees when there is common access control.

(Isn't it scary when Costin and I agree about anything ... that's *twice*
now!  :-)

>
> Costin

Craig


Reply via email to