[EMAIL PROTECTED] wrote:
> 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 ).

Just to be clear, I'm suggesting a single list for each package -- dev
and user combined, a commons-general list, and a list for the sandbox,
where people can work on unreleased packages (that don't have a list
yet). 

> jakarta-commons-DBCP
> jakarta-commons-digester
> jakarta-commons- ...
> jakarta-commons-general
> jakarta-commons-sandbox

For announcements, we should use jakarta-announce (often, I hope ;-). 

> Why not having a single CVS tree, with separate top-level dirs ?
> This seems to work fine in taglibs and catalina.

+1

> I agree, for agora/sandbox we need a separate CVS ( given the access
> control ).

+1

Reply via email to