lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Miller <markrmil...@gmail.com>
Subject Re: Lucene RC2
Date Fri, 04 Sep 2009 22:20:54 GMT
+1 - I'm not against knowing what the last rev upgraded to was - I also
think thats important. It just seems the Changes log should read what
changed from 1.3 or else its a little confusing. You could make another
argument with so many on trunk - but in my mind, the only thing those
going from 1.3 to 1.4 should need to worry about is upgraded to 2.9 -
not follow the whole dev path as changes invalidate changes. Not a big
deal if I am the only one that thinks that, just a thought. If we didn't
do it in general, it wouldn't matter if we didn't do with the Lucene
upgrade though.

- Mark

Grant Ingersoll wrote:
> It's very useful to know the rev # in a place that doesn't require: 1)
> starting up Solr, 2) unpacking the Lucene jar, but yeah, we could just
> have one entry at the top or something that just lists what the
> current version and rev # are.
>
> On Sep 4, 2009, at 2:41 PM, Mark Miller wrote:
>
>> I keep sending emails from the wrong account: attempt 2:
>>
>> I think it's kind of weird how we add an entry every update - IMO it
>> should be one entry- upgraded to Lucene 2.9. That's going to be the
>> only change.
>>
>> - Mark
>>
>> http://www.lucidimagination.com (mobile)
>>
>> On Sep 4, 2009, at 12:03 PM, Grant Ingersoll <gsingers@apache.org>
>> wrote:
>>
>>>
>>> On Aug 29, 2009, at 3:38 PM, Yonik Seeley wrote:
>>>
>>>> On Sat, Aug 29, 2009 at 5:44 PM, Bill Au<bill.w.au@gmail.com> wrote:
>>>>> Yonik,
>>>>>    Are you in the process of trying it out or upgrading Solr, or
>>>>> both?
>>>>> Bill
>>>>
>>>> It's done: http://svn.apache.org/viewvc?view=rev&revision=809010
>>>
>>> You should add a note to CHANGES.txt.
>
>


-- 
- Mark

http://www.lucidimagination.com




Mime
View raw message