Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Date: Tue, 8 Sep 2009 16:14:45 -0700 (PDT)
From: Chris Hostetter <hossman_lucene@fucit.org>
To: solr-dev@lucene.apache.org
Subject: Re: Lucene RC2
In-Reply-To: <4AA192C6.3010500@gmail.com>
Message-ID: <Pine.LNX.4.64.0909081612190.28957@radix.cryptio.net>
References: <0852AB8D-D4CE-4EA3-B0F8-8AB80D5EBF23@apache.org>
 <c68e39170908281232i1a864816x703e1d83f2d4a76b@mail.gmail.com>
 <3b5f72030908291444u60dad356h6a32371477bf945c@mail.gmail.com>
 <c68e39170908291538j4b5c3eddi1e6d0b36b9c63b50@mail.gmail.com>
 <8EF7E129-C345-44CF-AA73-CF9282A9C582@apache.org>
 <CB864FC5-BF31-42E0-9A23-12ED7359762F@gmail.com>
 <04413E69-6465-4F14-896A-EE8C66A309D3@apache.org>
 <4AA192C6.3010500@gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


: 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

it's equally important that people experimenting with trunk/nightlys have 
an easy way to distibguish what's changed between the version their using 
and the current version, so CHANGES.txt should be updated for every change 
-- but that "update" doesn't need to be purely additive, it can be an 
"edit" of an existing item in which case diffing the two versions of 
CHANGES.txt will still tell you what you need to know.


-Hoss