You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2016/10/30 20:33:09 UTC
Re: Towards Jena 3.1.1
When the export updates are in, I'll start the 3.1.1 release process
(exactly when subject to time available!).
Unless ...?
Andy
Re: Towards Jena 3.1.1
Posted by Andy Seaborne <an...@apache.org>.
On 01/11/16 13:52, A. Soroka wrote:
> I do not think I have anywhere near enough experience yet to RM, but I would like to be as involved as is convenient so that at some future point, I _can_ do a release.
>
> ---
> A. Soroka
> The University of Virginia Library
The instructions are at
https://cwiki.apache.org/confluence/display/JENA/Release+Process so have
a read and ask any questions. Its long because the instructions are
comprehensive.
It's good to set up a clean-room area - I use a different settings.xml
with the maven repo pointing to a special one where I can clean it
completely by deleting it.
You do the prep stages locally just to try them out.
Also
- get a feel for the Nexus server at http://repository.apache.org/
- setup for step 10 (uploading the bytes to
https://dist.apache.org/repos/dist/dev/jena
It all helps to get familiar and not have to do setup work while
following the process. When you want to do it for real, there is less of
a learning curve (and less to go wrong!) at that point in time.
Andy
Re: Towards Jena 3.1.1
Posted by "A. Soroka" <aj...@virginia.edu>.
I do not think I have anywhere near enough experience yet to RM, but I would like to be as involved as is convenient so that at some future point, I _can_ do a release.
---
A. Soroka
The University of Virginia Library
> On Nov 1, 2016, at 9:50 AM, Andy Seaborne <an...@apache.org> wrote:
>
> Now that the export registration is done, this release can be started. It'll have to done around other work unless someone else wants to RM it. At this point, it is a matter of executing the process at:
>
> https://cwiki.apache.org/confluence/display/JENA/Release+Process
>
> I have taken a clean local clone of the repo so if any last, last minute fixes go in, please make sure I know about them.
>
> Andy
Re: Towards Jena 3.1.1
Posted by Andy Seaborne <an...@apache.org>.
Now that the export registration is done, this release can be started.
It'll have to done around other work unless someone else wants to RM it.
At this point, it is a matter of executing the process at:
https://cwiki.apache.org/confluence/display/JENA/Release+Process
I have taken a clean local clone of the repo so if any last, last minute
fixes go in, please make sure I know about them.
Andy
Re: Towards Jena 3.1.1
Posted by "A. Soroka" <aj...@virginia.edu>.
There absolutely will be migration instructions with examples (by type of HttpAuthenticator)-- I was asking more specifically whether it seems like the specific case of this migration deserves a new section in that page, considering that it will have a limited lifespan. But maybe I'll just write the content and we can fix it up and format it as desired.
---
A. Soroka
The University of Virginia Library
> On Oct 31, 2016, at 7:20 AM, Rob Vesse <rv...@dotnetrdf.org> wrote:
>
> I would certainly like to see some migration content. I have a number of other projects which utilise existing API all of which will need to be appropriately updated
>
> Rob
>
> On 30/10/2016 20:44, "A. Soroka" <aj...@virginia.edu> wrote:
>
> +1 from my end.
>
> On that note (releasing) I need to edit:
>
> https://jena.apache.org/documentation/query/http-auth.html
>
> to document the changes in HTTP in 3.1.1 and give examples for authN scenarios using HttpContext. I was thinking maybe to add a "Migrating from HttpAuthenticator" section. Worthwhile or too release-specific?
>
> ---
> A. Soroka
> The University of Virginia Library
>
>> On Oct 30, 2016, at 4:33 PM, Andy Seaborne <an...@apache.org> wrote:
>>
>> When the export updates are in, I'll start the 3.1.1 release process (exactly when subject to time available!).
>>
>> Unless ...?
>>
>> Andy
>>
>
>
>
>
>
>
Re: Towards Jena 3.1.1
Posted by Rob Vesse <rv...@dotnetrdf.org>.
I would certainly like to see some migration content. I have a number of other projects which utilise existing API all of which will need to be appropriately updated
Rob
On 30/10/2016 20:44, "A. Soroka" <aj...@virginia.edu> wrote:
+1 from my end.
On that note (releasing) I need to edit:
https://jena.apache.org/documentation/query/http-auth.html
to document the changes in HTTP in 3.1.1 and give examples for authN scenarios using HttpContext. I was thinking maybe to add a "Migrating from HttpAuthenticator" section. Worthwhile or too release-specific?
---
A. Soroka
The University of Virginia Library
> On Oct 30, 2016, at 4:33 PM, Andy Seaborne <an...@apache.org> wrote:
>
> When the export updates are in, I'll start the 3.1.1 release process (exactly when subject to time available!).
>
> Unless ...?
>
> Andy
>
Re: Towards Jena 3.1.1
Posted by "A. Soroka" <aj...@virginia.edu>.
+1 from my end.
On that note (releasing) I need to edit:
https://jena.apache.org/documentation/query/http-auth.html
to document the changes in HTTP in 3.1.1 and give examples for authN scenarios using HttpContext. I was thinking maybe to add a "Migrating from HttpAuthenticator" section. Worthwhile or too release-specific?
---
A. Soroka
The University of Virginia Library
> On Oct 30, 2016, at 4:33 PM, Andy Seaborne <an...@apache.org> wrote:
>
> When the export updates are in, I'll start the 3.1.1 release process (exactly when subject to time available!).
>
> Unless ...?
>
> Andy
>
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
>
>
Re: Towards Jena 3.1.1
Posted by Osma Suominen <os...@helsinki.fi>.
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