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

Alexandre Rafalovitch commented on LUCENE-7543:
-----------------------------------------------

Sorry. You can stay at -1 :-) I do not see this as a rational trade-off of 
effort. 

I assume, the doap file will be updated by a release-manager already following 
a bunch of checklist items. Updated approximately once every 6 week!!!  Having 
one more that says "and remember to use x.y.z" version would have been 
sufficient. The build failure during generation of the *changes.html* would 
ensure the step is not skipped accidentally.

I appreciate your attempts to find a common ground. I just think we spent too 
much time disagreeing. Let's just go ahead and keep this for historical 
reference for when we actually have tools consuming this format and we can see 
what makes sense.


> Make changes-to-html target an offline operation
> ------------------------------------------------
>
>                 Key: LUCENE-7543
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7543
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Steve Rowe
>            Assignee: Steve Rowe
>             Fix For: master (7.0), 6.0.2, 6.1.1, 5.6, 5.5.4, 6.2.2, 6.4, 6.3.1
>
>         Attachments: LUCENE-7543-drop-XML-Simple.patch, LUCENE-7543.patch, 
> LUCENE-7543.patch, LUCENE-7543.patch
>
>
> Currently changes-to-html pulls release dates from JIRA, and so fails when 
> JIRA is inaccessible (e.g. from behind a firewall).
> SOLR-9711 advocates adding a build sysprop to ignore JIRA connection 
> failures, but I'd rather make the operation always offline.
> In an offline discussion, [~hossman] advocated moving Lucene's and Solr's 
> {{doap.rdf}} files, which contain all of the release dates that the 
> changes-to-html now pulls from JIRA, from the CMS Subversion repository 
> (downloadable from the website at http://lucene.apache.org/core/doap.rdf and 
> http://lucene.apache.org/solr/doap.rdf) to the Lucene/Solr git repository. If 
> we did that, then the process could be entirely offline if release dates were 
> taken from the local {{doap.rdf}} files instead of downloaded from JIRA.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to