lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-2747) Include formatted Changes.html for release
Date Wed, 29 Aug 2012 17:14:07 GMT

    [ https://issues.apache.org/jira/browse/SOLR-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444215#comment-13444215
] 

Steven Rowe edited comment on SOLR-2747 at 8/30/12 4:13 AM:
------------------------------------------------------------

bq. the patch i sent to the ML:

Cool, thanks, I was able to successfully run {{ant prepare-release-no-sign}} under {{solr/}}
locally after applying your patch.  I'll commit to branch_4x and trunk shortly.

bq. But we should decide where we want the output to go in the solr src dist, and also if
we should run it on the lucene CHANGES too and consolidate it in some way.

I think {{solr/docs/changes/}} is fine for the target directory.  

AFAICT, no form of Lucene's CHANGES.txt has ever been included in a Solr release.  I think
it's a good idea, though.  It could live at {{solr/docs/changes/Lucene-Changes.html}}.

Along these lines, the Solr News page could include a link to Lucene's {{Changes.html}} alongside
the link to the Solr {{Changes.html}} (I'm assuming that, as on the Lucene News page, the
{{CHANGES.txt}} link will actually be to the formatted {{Changes.html}}, once the functionality
provided by this issue has stabilized.)
                
      was (Author: steve_rowe):
    bq. the patch i sent to the ML:

Cool, thanks, I was able to successfully run {{ant prepare-release-no-sign}} under {{solr/}}
locally after applying your patch.  I'll commit to branch_4x and trunk shortly.

bq. But we should decide where we want the output to go in the solr src dist, and also if
we should run it on the lucene CHANGES too and consolidate it in some way.

I think {{solr/docs/changes/}} is fine for the target directory.  

AFAICT, no form of Lucene's CHANGES.txt has ever been included in a Solr release.  I think
it's a good idea, though.  It could live at {{solr/docs/changes/Lucene-Changes.html}}.

Along these lines, the Solr News page could include a link to Lucene's {{Changes.html}} alongside
the link to the Solr {{Changes.html}} (I'm assuming that, as on the Lucene News page, the
{{CHANGES.txt}} link will actually be to the formatted {{Changes.html}}, once the functionality
provided by this patch has stabilized.)
                  
> Include formatted Changes.html for release
> ------------------------------------------
>
>                 Key: SOLR-2747
>                 URL: https://issues.apache.org/jira/browse/SOLR-2747
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Martijn van Groningen
>            Assignee: Steven Rowe
>            Priority: Minor
>             Fix For: 4.0, 5.0
>
>         Attachments: SOLR-2747_fix.patch, SOLR-2747.patch, SOLR-2747.patch, SOLR-2747.patch,
SOLR-2747.patch, SOLR-2747.patch
>
>
> Just like when releasing Lucene, Solr should also have a html formatted changes file.
> The Lucene Perl script (lucene/src/site/changes/changes2html.pl) should be reused.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message