I see that the "issues fixed" part of the release artifacts is omitted. I presume this is intentional, probably because the number of issues in this release ( ~198 ) would break the auto generation of this report.
One reason for including this in the release is because the alternative, namely linking to the Jira website page for this version, is not "frozen" - it could be updated at any point in time, by anyone with Jira authoring capability, including after the release. We should probably have a consensus around including or omitting the issues-fixed part of the release. I think it is probably OK, as I don't think there's much use made of this, and the jira website report could serve adequately. What do others think? -Marshall On 7/20/2016 2:43 PM, Jaroslaw Cwiklik wrote: > Hi, > > the UIMA-DUCC 2.1.0 release candidate 3 is ready for voting. > > This version contains the following changes for issues found in RC2: > > - Updated RELEASE_NOTES > - Updated binary LICENSE > > The list of all changes in Jira: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%20%222.1.0-Ducc%22%20ORDER%20BY%20key%20ASC > > The source and binary zip/tars are staged here: > https://dist.apache.org/repos/dist/dev/uima/uima-ducc/2.1.0/RC3/ > > The Maven artifacts are here: > https://repository.apache.org/content/repositories/orgapacheuima-1101 > > The SVN tags are here: > http://svn.apache.org/repos/asf/uima/uima-ducc/tags/uima-ducc-2.1.0/ > > See http://uima.apache.org/testing-builds.html for suggestions on how to > test > release candidates. > > Please vote on release: > > [ ] +1 OK to release > [ ] 0 Don't care > [ ] -1 Not OK to release, because ... > > Thanks. >
