You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Osma Suominen <os...@helsinki.fi> on 2016/11/01 13:49:26 UTC

Re: Towards Jena 3.1.1

On 30/10/16 22:33, Andy Seaborne wrote:
> When the export updates are in, I'll start the 3.1.1 release process
> (exactly when subject to time available!).
>
> Unless ...?

https://issues.apache.org/jira/browse/JENA-1257

Sorry for not catching this earlier. But I think this needs 
investigation before we can release.

-Osma


-- 
Osma Suominen
D.Sc. (Tech), Information Systems Specialist
National Library of Finland
P.O. Box 26 (Kaikukatu 4)
00014 HELSINGIN YLIOPISTO
Tel. +358 50 3199529
osma.suominen@helsinki.fi
http://www.nationallibrary.fi

Re: Towards Jena 3.1.1

Posted by Osma Suominen <os...@helsinki.fi>.
01.11.2016, 16:32, Andy Seaborne kirjoitti:

> I heard about that was 9am this morning (my time) on users@.

Yes, I only noticed it yesterday afternoon.

> There is something to investigate but I think it is better is to release
> 3.1.1 now and do 3.1.2 shortly afterwards if needed.  The reason for the
> 3.1.0, 3.1.1 change should be recorded in JIRA somewhere.

Okay with me.

> In fact, I'd like us to be releasing more frequently (3 monthly?)
> because the long gap has caused (3.1.0, 3.1.1) there to be a lot of prep
> work as things get cleared up.

+1

-Osma


-- 
Osma Suominen
D.Sc. (Tech), Information Systems Specialist
National Library of Finland
P.O. Box 26 (Kaikukatu 4)
00014 HELSINGIN YLIOPISTO
Tel. +358 50 3199529
osma.suominen@helsinki.fi
http://www.nationallibrary.fi

Re: Towards Jena 3.1.1

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

On 01/11/16 13:49, Osma Suominen wrote:
> On 30/10/16 22:33, Andy Seaborne wrote:
>> When the export updates are in, I'll start the 3.1.1 release process
>> (exactly when subject to time available!).
>>
>> Unless ...?
>
> https://issues.apache.org/jira/browse/JENA-1257
>
> Sorry for not catching this earlier. But I think this needs
> investigation before we can release.

I heard about that was 9am this morning (my time) on users@.

There is something to investigate but I think it is better is to release 
3.1.1 now and do 3.1.2 shortly afterwards if needed.  The reason for the 
3.1.0, 3.1.1 change should be recorded in JIRA somewhere.

In fact, I'd like us to be releasing more frequently (3 monthly?) 
because the long gap has caused (3.1.0, 3.1.1) there to be a lot of prep 
work as things get cleared up.

	Andy

>
> -Osma
>
>