D]>
To: Lucene Dev
Sent: Wednesday, June 21, 2006 3:43:23 AM
Subject: Re: Core vs Contrib
: I think that it might be good to define 3 levels:
: fundamental - what all programs probably will use
: useful - what many programs might use
: contrib - mostly examples and code that is not quite ready to
tribute it, or at
least that's what I've observed.
Otis
- Original Message
From: Chris Hostetter <[EMAIL PROTECTED]>
To: Lucene Dev
Sent: Wednesday, June 21, 2006 3:43:23 AM
Subject: Re: Core vs Contrib
: I think that it might be good to define 3 levels:
: fund
On Jun 21, 2006, at 3:43 AM, Chris Hostetter wrote:
: I think that it might be good to define 3 levels:
: fundamental - what all programs probably will use
: useful - what many programs might use
: contrib - mostly examples and code that is not quite ready to be
: classed as useful
Those thre
: I think that it might be good to define 3 levels:
: fundamental - what all programs probably will use
: useful - what many programs might use
: contrib - mostly examples and code that is not quite ready to be
: classed as useful
Those three levels make sense -- but they don't map to what's curr
I think that it might be good to define 3 levels:
fundamental - what all programs probably will use
useful - what many programs might use
and
contrib - mostly examples and code that is not quite ready to be
classed as useful
On Jun 16, 2006, at 6:03 PM, Chris Hostetter wrote:
Are there any
Are there any written (or unwritten) guidelines on when something should
be commited to the core code base vs when a contrib module should be used?
Obviously if a new feature rquires changing APIs omodifying one of the
existing core classes, then that kind of needs to be in the core -- and
there
