[
https://issues.apache.org/jira/browse/JENA-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361864#comment-14361864
]
Andy Seaborne commented on JENA-896:
------------------------------------
The referenced email only suggests removing them.
While it would be ideal to have a perfect history of changes for each release,
that information is already available in JIRA, which provides custom sorting
and searching, including focusing in on particular components of interest.
Maintaining the ReleaseNotes (for modules that have them) is clearly not
something that is happening. It duplicates JIRA.
Any increase in work on the release process should have a high barrier for
inclusion in the process steps. We already have the announcement message so I
think it would be best to invest time on the announcement message as a
communication channel.
> 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)
