[
https://issues.apache.org/jira/browse/JENA-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361886#comment-14361886
]
Andy Seaborne commented on JENA-896:
------------------------------------
Current situation:
{noformat}
jena-arq/ReleaseNotes.txt
jena-core/ReleaseNotes.txt
jena-csv/ReleaseNotes.txt
jena-fuseki1/ReleaseNotes.txt
jena-fuseki2/ReleaseNotes.txt
jena-iri/RELEASE_NOTES.txt
jena-sdb/ChangeLog.txt
jena-spatial/ReleaseNotes.txt
jena-tdb/ReleaseNotes.txt
jena-text/ReleaseNotes.txt
{noformat}
They record "significant" (no definition) changes, not every change made, so
bug fixes etc that are just the usual maintenance don't seem to be there. What
they do sometimes include is minor features. The entire mechanism predates use
of JIRA and we are getting more systematic about JIRA over time as well.
Ones for legacy/in-maintenance modules are particularly lagging (I'm guilt of
that; It's hard to be motivated to do recording twice).
> Remove ReleaseNotes.txt from releases
> -------------------------------------
>
> Key: JENA-896
> URL: https://issues.apache.org/jira/browse/JENA-896
> Project: Apache Jena
> Issue Type: Task
> Components: Documentation, Web site
> Affects Versions: Jena 2.13.0
> Reporter: Stian Soiland-Reyes
>
> The [release notes of 2.13.0
> RC1|https://github.com/apache/jena/blob/ecaa41eefdcb79f16bd4b9525b89309f8282ca47/jena-core/ReleaseNotes.txt]
> were not updated to mention 2.13.0
> It was [suggested for future
> releases|http://mail-archives.apache.org/mod_mbox/jena-dev/201503.mbox/%3C54FD8D9D.8020206%40apache.org%3E]
> to remove these ReleaseNotes from the releases as they require manual
> updating - and instead include a fixed URL to page(s) that describes the
> change log. This may be an auto-generated page in Jira or a page on the
> website, with links to Jira.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
