On 2/12/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
> On Tue, 2006-02-07 at 12:37 -0500, Rahul Akolkar wrote:
> > On 2/7/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
> > > Specifically with respect to Latka, but applicable to all Commons 
> > > components.
> > <snip/>
> >
> > Thanks for bringing this up, its been something I (and possibly
> > others) have been wondering as well.
> >
> > Add EL to that starting list.
>
> EL is actually an interesting example...
>
> > > How do we want to handle released (ie non-sandboxed) components that
> > > have gone dormant? Do we add a new component called Legacy (or
> > > something like that)?
> > >
> > <snap/>
> >
> > Ofcourse we do. As Robert points out there may be separate "legacy"
> > and "matured beyond belief" categories (even though the second
> > category has extremely limited membership, IMO), but the undercurrent
> > still holds -- some components are not supported as well as we'd hope
> > (I just browsed the archives for unanswered questions, and bugzilla
> > for unanswered tickets).
>
> legacy would be a very misleading term for EL. EL is definitely
> finished.
>
> i wonder whether there's something like a main sequence for components:
>
> sandbox -> immature (aka unreleased) -> stable -> mature -> finished
>
> and whether we could make use of it...

Have to allow for loops.  Some things go dormant for a while and then
"wake up" again.  I am not sure what problem we are trying to solve
here.  If it is making it clear what components are not being actively
supported, I am +1, if it is declaring things "finished" I see no
point in that, and potentially some loss in doing it (discourages
contributions to "finished" components).

Phil

>
> - robert
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to