[
https://issues.apache.org/jira/browse/LUCENE-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664311#comment-15664311
]
Steve Rowe commented on LUCENE-7543:
------------------------------------
bq. So, what uses doap.rdf and how is it kept up to date?
I'm not sure what uses it, but keeping it up-to-date is part of the ReleaseToDo.
bq. And if it is moved to GitHub, do we abandon the original location/processes?
It won't be moved to GitHub of course, but rather to the Apache Git repo.
These files are currently hosted in the Lucene/Solr CMS-based website
repository. An extra release step will be required if we move it to the Git
repo, so that the files will continue to be present on the website, similarly
to how javadocs are now copied to the website. (I don't think keeping two
copies of these files, one in Git and one in the CMS repo, would be a good
alternative.)
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
