lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-3164) consolidate various CHANGES.txt into two files: lucene and solr
Date Tue, 31 May 2011 05:18:47 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041429#comment-13041429
] 

Robert Muir commented on LUCENE-3164:
-------------------------------------

{quote}
What are your thoughts about trunk in this regard - would you like there 3 changes files,
i.e. keep one for modules?
{quote}

I guess I'd still like to say CHANGES should correspond to a product. If modules was actually
a lucene-subproject, then
I would say yes it should have a CHANGES, but I don't think thats what it is, and I'm not
sure thats what we want it to be.

Currently its described as "shared code" between lucene and solr, but its such a work in progress
its hard to tell...
Maybe next week someone proposes a huge refactoring of lucene core into modules/index, modules/codecs,
modules/search or 
something (we could still produce one jar file, this is just about how we manage the source!)

I guess thats my personal opinion of what I'd love to see happen, that lucene/ goes away and
our source code really is
modular and organized in a way that makes sense... and that all the code in there is first-class
(no contribs), if we 
want a sandbox we can do that somewhere else.

Having said all this, I know I didn't actually answer your question... I guess for now we
could have a third CHANGES file
at least temporarily until we figure it all out? 3 is still a lot better than 12, but 2 would
be best!


> consolidate various CHANGES.txt into two files: lucene and solr
> ---------------------------------------------------------------
>
>                 Key: LUCENE-3164
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3164
>             Project: Lucene - Java
>          Issue Type: Task
>            Reporter: Robert Muir
>
> There are CHANGES.txt files everywhere: lucene/contrib has a CHANGES.txt, the benchmark
package has its own CHANGES.txt, in trunk all the modules have their own CHANGES.txt, and
each solr contrib has its own CHANGES.txt
> I propose we merge these files into a CHANGES.txt for each "product" we make. so that
means lucene/CHANGES.txt and solr/CHANGES.txt

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message