[
https://issues.apache.org/jira/browse/LUCENE-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646028#comment-15646028
]
Alexandre Rafalovitch commented on LUCENE-7543:
-----------------------------------------------
Just to clarify.
Currently the (perl) script pulls the information from JIRA, right? So, it is
maintained as part of the issue tagging/release process.
So, what uses doap.rdf and how is it kept up to date? And if it is moved to
GitHub, do we abandon the original location/processes?
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
