[
https://issues.apache.org/jira/browse/LUCENE-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677268#comment-15677268
]
Steve Rowe commented on LUCENE-7543:
------------------------------------
With your first patch I ran {{ant changes-to-html}} in {{lucene/}} and I see
many releases' dates missing. I double checked that this is a new problem by
looking at [http://lucene.apache.org/core/6_3_0/changes/Changes.html], which
doesn't have this problem. A nit: the 6.3.0 release date looks weird because
the day-of-month is single digit (unlike all other dates, where it's
zero-padded).
bq. Ok, I added the versions from the jira json. However, the "-final", "RCx"
and "1.01b" releases are not in any source. Is it ok to add them into the RDF
as-is?
BTW, the "RCx" releases were treated as if they were real releases at the time,
more like -alpha, -beta, etc. than "release candidate" really. The only thing
I think worth considering here is whether the "final" modifier should be
stripped in the doap.rdf files (even though it will remain in
CHANGES.txt/Changes.html). I could go either way. I notice that JIRA lists
"1.9 final" as just "1.9" - this is consistent with both the "-alpha/-beta" and
"-RCx" naming schemes. The distributions at
[http://archive.apache.org/dist/lucene/java/archive/] include the "-final" and
"-rcX" suffixes in their names, though, so I'd prefer to continue naming these
releases in the doap.rdf files the same way as they are named in CHANGES.txt
(i.e., include " final" in their names). This has the nice side-effect that no
extra mapping step will be required in {{changes2html.pl}}.
> 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
> Attachments: 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
