lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grant Ingersoll <gsing...@apache.org>
Subject Re: CHANGES.txt karma
Date Wed, 20 Aug 2008 14:34:02 GMT
One other solution I just thought of is we could move CHANGES.txt to  
the docs directory and during packaging, copy it up to the top level.   
The upside to this is contrib committers would have the ability to  
commit to it, the downside is it isn't immediately obvious to casual  
viewers of the source code.

Thoughts?

-Grant

On Jun 27, 2008, at 1:02 PM, Karl Wettin wrote:

> Yeah, I saw the response there. Should it be a single changes for  
> contrib, or one per contrib module?
>
>      karl
>
> 27 jun 2008 kl. 00.46 skrev Grant Ingersoll:
>
>> One alternative, in the short term, is to keep a CHANGES on a per  
>> contrib basis...  I realize that is less than ideal.  I've asked on  
>> infra
>>
>>
>> On Jun 26, 2008, at 3:43 PM, Grant Ingersoll wrote:
>>
>>> Hmmm, true...   Let me see if we can do per file karma.
>>>
>>> -Grant
>>>
>>> On Jun 26, 2008, at 1:03 PM, Karl Wettin wrote:
>>>
>>>> Contrib committers does not seem to have karma to trunk/ 
>>>> CHANGES.txt.
>>>>
>>>>
>>>>     karl
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
>>>> For additional commands, e-mail: java-dev-help@lucene.apache.org
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: java-dev-help@lucene.apache.org
>>>
>>

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


Mime
View raw message