RC1 cancelled because of because of JENA-1817, the report from Aaron.
https://issues.apache.org/jira/browse/JENA-1817.
Good thing this was caught!
I'll produce RC2 with only:
(1) Revert version
(2) the change needed for JENA-1817
That should make checking the next RC easier for everyone.
Andy
On 13/01/2020 16:23, Andy Seaborne wrote:
Hi,
Here is a vote on the release of Apache Jena 3.14.0
This is the first proposed release candidate.
==== Changes:
https://s.apache.org/jena-3.14.0-jira
==== Release Vote
Everyone, not just committers, is invited to test and vote.
Please download and test the proposed release.
Staging repository:
https://repository.apache.org/content/repositories/orgapachejena-1035
Proposed dist/ area:
https://dist.apache.org/repos/dist/dev/jena/
Keys:
https://svn.apache.org/repos/asf/jena/dist/KEYS
Git commit (browser URL):
https://github.com/apache/jena/commit/19d42a5
Git Commit Hash:
19d42a57a9debc675047b2d1ce9769979c43e7d8
Git Commit Tag:
jena-3.14.0
Please vote to approve this release:
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This vote will be open until at least
Thursday, 16th January 2020 at 187:00 UTC
If you expect to check the release but the time limit does not work
for you, please email within the schedule above with an expected time
and we can extend the vote period.
Thanks,
Andy
Checking needed:
+ are the GPG signatures fine?
+ are the checksums correct?
+ is there a source archive?
+ can the source archive really be built?
(NB This requires a "mvn install" first time)
+ is there a correct LICENSE and NOTICE file in each artifact
(both source and binary artifacts)?
+ does the NOTICE file contain all necessary attributions?
+ have any licenses of dependencies changed due to upgrades?
if so have LICENSE and NOTICE been upgraded appropriately?
+ does the tag/commit in the SCM contain reproducible sources?
