The current status is that we have
3 +1 binding
1 -1 non-binding
I am concerned about the expectations here.
Osma very kindly tested the build in his environment which I think is
above-and-beyond the requirements for voting. Thank you, Osma.
The release was signalled 18 April.
Dev builds happen every day.
If testing only starts on a release candidate and not development
builds, and that testing is coupled to gating the release, we not going
to make progress.
Like any system, we release with JIRA that are open. So create new JIRA
and consider the overall context. Making certain new issues gating
criteria on a release when normally they would be JIRA items is making
them too important.
Are users and downstream integrators helped or hindered by delay?
We can end up either with repeated release attempts or need to
separately release different modules or having formal RC releases, the
last two mean more votes and more Release Manager time.
At this point, I will offer to be Release Manager for a 3.1.1 release in
1-2 months time (if anything gets fixed) but blocking 3.1.0 now on
previously unreported issues is blocking all the other good things in 3.1.0.
Release early, release often.
Andy
PS
It takes a long time (elapsed) to sort out OSGi issues. We now have
competing views of OSGi usage.
An option is to release 3.1.0 without an OSGi bundle, just the source code.
On 04/05/16 20:53, Andy Seaborne wrote:
Hi,
Here is a vote on a release of Jena 3.1.0
(with Fuseki 2.4.0 and Fuseki 1.4.0).
This is the second proposed candidate for this release.
This fixes, from the previous proposed candidate
1/ Presence of binaries in the source-release
2/ Jump in large size of binary downloads due to javadoc inclusion
* Dependency changes:
Upgrades:
jsonld-java : 2.8.2
jackson 2.6.3
slf4j 1.7.20
dexx collections 0.6
Key features listed below.
Everyone, not just committers, is invited to test and vote.
Staging repository:
https://repository.apache.org/content/repositories/orgapachejena-1012/
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):
http://git-wip-us.apache.org/repos/asf/jena/commit/e7ee6bb6
Git Commit Hash:
e7ee6bb69a5d7ce930a2529dd576a9ea209596a3
Git Commit Tag:
jena-3.1.0-rc3
Please vote to approve this release:
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This vote will be open to at least
7th May 2016, 23:59 UTC
If you expect to check the release but the 72 hour 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:
+ does everything work on Linux?
+ does everything work on MS Windows?
+ does everything work on OS X?
+ are the GPG signatures fine?
+ are the checksums correct?
+ is there a source archive?
+ can the source archive really be built?
+ 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?
---------------------------
Key features of the release:
* In-memory txn dataset (Adam Soroka) (RC in 3.0.1)
http://jena.staging.apache.org/documentation/rdf/datasets.html
* Quads (Qihong Lin) (RC in 3.0.1)
http://jena.staging.apache.org/documentation/query/construct-quad.html
* DatasetGraphs & transactions integration
* Alternative QueryParsers in jena-text
* new module jena-cmds
"jena.*"
* Fuseki: Multiple service per file, shared datasets
* Logging
log4j marked <optional>
* New custom functions and aggregate functions
Added:
* afn:springf (contribution from Alessandro Seganti)
* The XQuery/XPath Functions and Operators "math:" functions
* Custom aggregates for stdev etc. (also STDEV etc as keywords).
* FactoryRDF
Parsing RDF now saves space by interning RDFTerms created
during a each parser run.
* OSGi fixes (Jaroslav Pullmann)
* General maintenance: about 80 JIRA.
