commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Ruby <>
Subject Re:
Date Tue, 17 Dec 2002 00:58:04 GMT
Stephen Colebourne wrote:
> In broader terms however:
> a) The status of both the [util] and [email] components within
> jakarta-commons-sandbox is that of unreleased code, no matter how stable.
> Deprecation is not required.

Indefinately?  Is that good for the [util], [email], commons, jakarta, 
or the ASF?

> b) The [util] component is generally viewed as a 'dumping ground' for code
> that doesn't fit in elsewhere, and might better be named 'misc' or
> 'homeless'. The changes were designed to give [util] a chance of a release.

...dumped and homeless...

> c) Commons must have the right to make changes to code and manage its own
> releases and components. This should apply whether it is code written
> specifically for commons, or donated to commons from another jakarta
> project. If this is not the case then commons is simply a 'dumping ground'
> for other jakarta projects hoping to off-load maintainance, rather than a
> vibrant community in its own right.

Self-managed would be nice.  Can you honestly say that's what we have now?

- Sam Ruby

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message