You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Jan Høydahl <ja...@cominvent.com> on 2016/09/27 12:35:29 UTC
LUCENE_CHANGES.txt???
Hi,
In Solr’s CHANGES.txt there is this line for every release since 4.10:
Consult the LUCENE_CHANGES.txt file for additional, low level, changes in this release.
But there is no file with that name…
Also, why don’t we add the release date for each release also to CHANGES.txt?
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: LUCENE_CHANGES.txt???
Posted by Jan Høydahl <ja...@cominvent.com>.
> LUCENE_CHANGES.txt should be in the binary and source release tarballs/zips - see SOLR-6342.
Ah, my bad, I did not notice that file before, so the reference is OK then :)
Regarding release date, I always use CHANGES.txt, not Changes.html
Also the HTML has the problem of not knowing the date of the current release btw, see http://lucene.apache.org/solr/6_2_1/changes/Changes.html <http://lucene.apache.org/solr/6_2_1/changes/Changes.html>
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 27. sep. 2016 kl. 17.02 skrev Steve Rowe <sa...@gmail.com>:
>
> LUCENE_CHANGES.txt should be in the binary and source release tarballs/zips - see SOLR-6342.
>
> The problem of all of the mentions linking to the same online HTML is known: SOLR-6384. I should fix that :).
>
> --
> Steve
> www.lucidworks.com
>
>> On Sep 27, 2016, at 10:01 AM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
>>
>> The HTML file generated links to the Lucene's version of the changes
>> HTML file. Unfortunately, ALL of the mentions link to the same
>> top-level point of that file, so are somewhat redundant.
>>
>> Also, the HTML version fills-in the exact release dates by extracting
>> them from JIRA's API.
>>
>> So, when we say "fix", what do we mean exactly?
>>
>> Regards,
>> Alex.
>> ----
>> Newsletter and resources for Solr beginners and intermediates:
>> http://www.solr-start.com/
>>
>>
>> On 27 September 2016 at 20:10, Jan Høydahl <ja...@cominvent.com> wrote:
>>> What if we for the version being released say “Release date: September 2016
>>> (current release, see exact date on release archive)”
>>> but when we create the section heading for the next release we also fill in
>>> the exact date for the previous one.
>>>
>>> --
>>> Jan Høydahl, search solution architect
>>> Cominvent AS - www.cominvent.com
>>>
>>> 27. sep. 2016 kl. 15.03 skrev Yonik Seeley <ys...@gmail.com>:
>>>
>>> Release dates were always a problem because one would have to guess
>>> when the vote would pass (and change the date every time a new RC is
>>> spun... error prone). Perhaps just add month+year?
>>>
>>> -Yonik
>>>
>>>
>>> On Tue, Sep 27, 2016 at 8:53 AM, David Smiley <da...@gmail.com>
>>> wrote:
>>>
>>> +1 to fix the reference to Lucene's CHANGES.txt and to add release dates.
>>>
>>> On Tue, Sep 27, 2016 at 8:36 AM Jan Høydahl <ja...@cominvent.com> wrote:
>>>
>>>
>>> Hi,
>>>
>>> In Solr’s CHANGES.txt there is this line for every release since 4.10:
>>>
>>> Consult the LUCENE_CHANGES.txt file for additional, low level, changes
>>> in this release.
>>>
>>> But there is no file with that name…
>>>
>>>
>>> Also, why don’t we add the release date for each release also to
>>> CHANGES.txt?
>>>
>>> --
>>> Jan Høydahl, search solution architect
>>> Cominvent AS - www.cominvent.com
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>> --
>>> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
>>> LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
>>> http://www.solrenterprisesearchserver.com
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
Re: LUCENE_CHANGES.txt???
Posted by Steve Rowe <sa...@gmail.com>.
LUCENE_CHANGES.txt should be in the binary and source release tarballs/zips - see SOLR-6342.
The problem of all of the mentions linking to the same online HTML is known: SOLR-6384. I should fix that :).
--
Steve
www.lucidworks.com
> On Sep 27, 2016, at 10:01 AM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
>
> The HTML file generated links to the Lucene's version of the changes
> HTML file. Unfortunately, ALL of the mentions link to the same
> top-level point of that file, so are somewhat redundant.
>
> Also, the HTML version fills-in the exact release dates by extracting
> them from JIRA's API.
>
> So, when we say "fix", what do we mean exactly?
>
> Regards,
> Alex.
> ----
> Newsletter and resources for Solr beginners and intermediates:
> http://www.solr-start.com/
>
>
> On 27 September 2016 at 20:10, Jan Høydahl <ja...@cominvent.com> wrote:
>> What if we for the version being released say “Release date: September 2016
>> (current release, see exact date on release archive)”
>> but when we create the section heading for the next release we also fill in
>> the exact date for the previous one.
>>
>> --
>> Jan Høydahl, search solution architect
>> Cominvent AS - www.cominvent.com
>>
>> 27. sep. 2016 kl. 15.03 skrev Yonik Seeley <ys...@gmail.com>:
>>
>> Release dates were always a problem because one would have to guess
>> when the vote would pass (and change the date every time a new RC is
>> spun... error prone). Perhaps just add month+year?
>>
>> -Yonik
>>
>>
>> On Tue, Sep 27, 2016 at 8:53 AM, David Smiley <da...@gmail.com>
>> wrote:
>>
>> +1 to fix the reference to Lucene's CHANGES.txt and to add release dates.
>>
>> On Tue, Sep 27, 2016 at 8:36 AM Jan Høydahl <ja...@cominvent.com> wrote:
>>
>>
>> Hi,
>>
>> In Solr’s CHANGES.txt there is this line for every release since 4.10:
>>
>> Consult the LUCENE_CHANGES.txt file for additional, low level, changes
>> in this release.
>>
>> But there is no file with that name…
>>
>>
>> Also, why don’t we add the release date for each release also to
>> CHANGES.txt?
>>
>> --
>> Jan Høydahl, search solution architect
>> Cominvent AS - www.cominvent.com
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>> --
>> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
>> LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
>> http://www.solrenterprisesearchserver.com
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: LUCENE_CHANGES.txt???
Posted by Alexandre Rafalovitch <ar...@gmail.com>.
The HTML file generated links to the Lucene's version of the changes
HTML file. Unfortunately, ALL of the mentions link to the same
top-level point of that file, so are somewhat redundant.
Also, the HTML version fills-in the exact release dates by extracting
them from JIRA's API.
So, when we say "fix", what do we mean exactly?
Regards,
Alex.
----
Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/
On 27 September 2016 at 20:10, Jan Høydahl <ja...@cominvent.com> wrote:
> What if we for the version being released say “Release date: September 2016
> (current release, see exact date on release archive)”
> but when we create the section heading for the next release we also fill in
> the exact date for the previous one.
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
> 27. sep. 2016 kl. 15.03 skrev Yonik Seeley <ys...@gmail.com>:
>
> Release dates were always a problem because one would have to guess
> when the vote would pass (and change the date every time a new RC is
> spun... error prone). Perhaps just add month+year?
>
> -Yonik
>
>
> On Tue, Sep 27, 2016 at 8:53 AM, David Smiley <da...@gmail.com>
> wrote:
>
> +1 to fix the reference to Lucene's CHANGES.txt and to add release dates.
>
> On Tue, Sep 27, 2016 at 8:36 AM Jan Høydahl <ja...@cominvent.com> wrote:
>
>
> Hi,
>
> In Solr’s CHANGES.txt there is this line for every release since 4.10:
>
> Consult the LUCENE_CHANGES.txt file for additional, low level, changes
> in this release.
>
> But there is no file with that name…
>
>
> Also, why don’t we add the release date for each release also to
> CHANGES.txt?
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
> --
> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
> LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
> http://www.solrenterprisesearchserver.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: LUCENE_CHANGES.txt???
Posted by Jan Høydahl <ja...@cominvent.com>.
What if we for the version being released say “Release date: September 2016 (current release, see exact date on release archive)”
but when we create the section heading for the next release we also fill in the exact date for the previous one.
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 27. sep. 2016 kl. 15.03 skrev Yonik Seeley <ys...@gmail.com>:
>
> Release dates were always a problem because one would have to guess
> when the vote would pass (and change the date every time a new RC is
> spun... error prone). Perhaps just add month+year?
>
> -Yonik
>
>
> On Tue, Sep 27, 2016 at 8:53 AM, David Smiley <da...@gmail.com> wrote:
>> +1 to fix the reference to Lucene's CHANGES.txt and to add release dates.
>>
>> On Tue, Sep 27, 2016 at 8:36 AM Jan Høydahl <ja...@cominvent.com> wrote:
>>>
>>> Hi,
>>>
>>> In Solr’s CHANGES.txt there is this line for every release since 4.10:
>>>
>>> Consult the LUCENE_CHANGES.txt file for additional, low level, changes
>>> in this release.
>>>
>>> But there is no file with that name…
>>>
>>>
>>> Also, why don’t we add the release date for each release also to
>>> CHANGES.txt?
>>>
>>> --
>>> Jan Høydahl, search solution architect
>>> Cominvent AS - www.cominvent.com
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>> --
>> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
>> LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
>> http://www.solrenterprisesearchserver.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
Re: LUCENE_CHANGES.txt???
Posted by Yonik Seeley <ys...@gmail.com>.
Release dates were always a problem because one would have to guess
when the vote would pass (and change the date every time a new RC is
spun... error prone). Perhaps just add month+year?
-Yonik
On Tue, Sep 27, 2016 at 8:53 AM, David Smiley <da...@gmail.com> wrote:
> +1 to fix the reference to Lucene's CHANGES.txt and to add release dates.
>
> On Tue, Sep 27, 2016 at 8:36 AM Jan Høydahl <ja...@cominvent.com> wrote:
>>
>> Hi,
>>
>> In Solr’s CHANGES.txt there is this line for every release since 4.10:
>>
>> Consult the LUCENE_CHANGES.txt file for additional, low level, changes
>> in this release.
>>
>> But there is no file with that name…
>>
>>
>> Also, why don’t we add the release date for each release also to
>> CHANGES.txt?
>>
>> --
>> Jan Høydahl, search solution architect
>> Cominvent AS - www.cominvent.com
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
> --
> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
> LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
> http://www.solrenterprisesearchserver.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: LUCENE_CHANGES.txt???
Posted by David Smiley <da...@gmail.com>.
+1 to fix the reference to Lucene's CHANGES.txt and to add release dates.
On Tue, Sep 27, 2016 at 8:36 AM Jan Høydahl <ja...@cominvent.com> wrote:
> Hi,
>
> In Solr’s CHANGES.txt there is this line for every release since 4.10:
>
> Consult the LUCENE_CHANGES.txt file for additional, low level, changes
> in this release.
>
> But there is no file with that name…
>
>
> Also, why don’t we add the release date for each release also to
> CHANGES.txt?
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
> --
Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker
LinkedIn: http://linkedin.com/in/davidwsmiley | Book:
http://www.solrenterprisesearchserver.com