Re: Propose CHANGES.txt releases begin with the categories (empty)

2019-07-08 Thread David Smiley
https://issues.apache.org/jira/browse/LUCENE-8883 and now with a simple patch ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Tue, Jun 25, 2019 at 3:45 AM Jan Høydahl wrote: > +1 > > PS: Check out the template in scripts/addVersion.py which now

Re: Propose CHANGES.txt releases begin with the categories (empty)

2019-06-25 Thread Jan Høydahl
+1 PS: Check out the template in scripts/addVersion.py which now just adds "(no changes)" -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 25. jun. 2019 kl. 09:02 skrev Adrien Grand : > > +1, it's otherwise tempting to reuse an existing category even if it >

Re: Propose CHANGES.txt releases begin with the categories (empty)

2019-06-25 Thread Adrien Grand
+1, it's otherwise tempting to reuse an existing category even if it doesn't fit as well as a category that is not listed yet. On Tue, Jun 25, 2019 at 6:40 AM David Smiley wrote: > > Looking at Solr's CHANGES.txt for 8.2 I see we have some sections: "Upgrade > Notes", "New Features", "Bug

Re: Propose CHANGES.txt releases begin with the categories (empty)

2019-06-24 Thread Mikhail Khludnev
It's fine, David. On Tue, Jun 25, 2019 at 7:40 AM David Smiley wrote: > Looking at Solr's CHANGES.txt for 8.2 I see we have some sections: > "Upgrade Notes", "New Features", "Bug Fixes", and "Other Changes". There > is no "Improvements" so no surprise here, the New Features category has >

Propose CHANGES.txt releases begin with the categories (empty)

2019-06-24 Thread David Smiley
Looking at Solr's CHANGES.txt for 8.2 I see we have some sections: "Upgrade Notes", "New Features", "Bug Fixes", and "Other Changes". There is no "Improvements" so no surprise here, the New Features category has issues that ought to be listed as such. I think the order vary as well. I