: http://www.nabble.com/Re%3A-Tika-Changelog-p11082404.html
:
: IMO, changes in implementation detail don't belong in CHANGES.txt,
: unless it's to give credit to a contributor for that change (which
: committers don't need).
:
: For example, the following change shouldn't matter to normal users:
: SOLR-262: Added toObject( Fieldable ) to FieldType. [...]
i agree with teh sentiments you posted to the tika list, but we have to
keep in mind that the scope of "users" is broad ... that note about
SOLR-262 may not be important to users that only deal with Solr out of the
box, but it is important to advanced users writing their own plugins --
and should be noted in teh CHANGES.txt somewhere ... but i would agree
that the "New Features" section probably isn't the right place for it.
this seems like a perfect example of the type of thing that belongs in
"Other Changes" ... or perhaps a new section in CHANGES specificly for
plugin developers. ("Internal Changes" maybe?)
-Hoss
