I renamed all current components, plus deleted two (contrib/analyzers and contrib/wikipedia).
core/codecs core/index core/other core/query/scoring core/queryparser core/search core/store core/termvectors general/build general/javadocs general/test general/website modules/analysis modules/benchmark modules/examples modules/grouping modules/highlighter modules/other modules/queryparser modules/spatial modules/spellchecker Shai On Mon, May 16, 2011 at 7:07 AM, Mark Miller <[email protected]> wrote: > > On May 15, 2011, at 10:42 PM, Shai Erera wrote: > > > I was aiming at avoiding that scenario. I think every issue should be > assigned to a specific component, and if there isn't one available, we > should create it. > > > Based on history and how these things normally go, unless you are planning > on spending a *lot* of time curating JIRA for the forceable future, this is > an unlikely outcome. Better categories will hopefully mean more compliance, > but I'd bet the standard hodgepodge of JIRA submissions and curation is > going to remain fairly similar to what we have seen. Version is a much more > important field - and even it is not curated even close to this 'ideal' > world level. > > I think every issue should be fully filled out, correctly filled out, cross > linked with all relevant issues, etc, etc. > > But I don't plan on it being the normal scenario ;) > > FWIW: I fill out component sometimes, and other times I'm just not worried > about it. Someone can always come along after us types and random users and > clean up after them, but I surmise that won't last long. > > - Mark Miller > lucidimagination.com > > Lucene/Solr User Conference > May 25-26, San Francisco > www.lucenerevolution.org > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
