You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "A. Soroka" <aj...@virginia.edu> on 2016/10/28 13:53:52 UTC

3.1.1 timing?

Do we have a sense of what remaining blockers exist for releasing 3.1.1?

I know that I have some documentation to write for breaking changes to the HTTP usage in ARQ, but I was thinking more of what remains to be done code-wise. I don't see anything in Jira with priority Blocker or open with fix release 3.1.1, but that doesn't necessarily prove anything. {grin}

---
A. Soroka
The University of Virginia Library


Re: 3.1.1 timing?

Posted by Andy Seaborne <an...@apache.org>.

On 28/10/16 14:53, A. Soroka wrote:
> Do we have a sense of what remaining blockers exist for releasing 3.1.1?

Soon, subject to finding time, as ever.

Please let me knwo if master has anything significant added.  I have set 
up for release and tested the process so I need to make sure I catch 
anything from now on no need to hold back on putting in bug fixes and 
safe changes etc etc.

I would like to get the export registration sorted out - Stian's PR is a 
good start though I don't read the regulations the same way so I need to 
go back and re-read.  Jena itself does not contain crypto software, it 
uses it.  So the only points we ship crypto are the distributions: 
apache-jena (binary), Fuseki1 (binary distribution and maven) and 
Fuseki2 (binary distribution and maven) -- the maven is for the uber 
jars and war file.

>
> I know that I have some documentation to write for breaking changes to the HTTP usage in ARQ, but I was thinking more of what remains to be done code-wise. I don't see anything in Jira with priority Blocker or open with fix release 3.1.1, but that doesn't necessarily prove anything. {grin}

We release regularly rather release by features/fixes.  3.1.1 and 3.1.0 
have turned out cumulatively a bit big - I'd like to release more 
frequently so that each release does not trigger a work bulge.  But 
separate conversation.

PR#176 could go in or not - as it is clean-up it does not really matter 
if it goes in or not.

The text index work looks very interesting but the major version change 
for Lucene (or 2 if it goes to v6) means it is not for this release IMO.

Anything I've missed?

     Andy

>
> ---
> A. Soroka
> The University of Virginia Library
>