:Re: Jena 2.10.0 - ready yet?
I happen to have Mario's store in my workspace and I didn't observe any
obvious issues in terms of compilation other than the package renames, but
I didn't run our test suite yet because some adaptations will (likely) be
required on his side. I&#x
On 13/02/13 14:17, Simon Helsen wrote:
I happen to have Mario's store in my workspace and I didn't observe any
obvious issues in terms of compilation other than the package renames, but
I didn't run our test suite yet because some adaptations will (likely) be
required on his side. I've asked Mari
r 2.10.0 and check if there are any
obvious issues or regressions.
Simon
From:
Andy Seaborne
To:
dev@jena.apache.org, Mario Ds Briggs ,
Date:
02/13/2013 04:43 AM
Subject:
Re: Jena 2.10.0 - ready yet?
Stephen,
Let's see how it goes - you mentioned 3-4 weeks, as did Rob, so I worked
bac
Stephen,
Let's see how it goes - you mentioned 3-4 weeks, as did Rob, so I worked
back from that and started ASAP. If things go well, we can start the
vote next week and have some overlap.
If you want to prompt on users@ and/or ping specific groups who we know
should be testing that will ac
Any chance we could accelerate the schedule a little bit? Maybe aim
for 1 week of user testing followed the formal release process? It
would happen to work out well for me if the release was final at least
a few days before the end of the month (around say the 25th or 26th).
All this baring any
: Jena 2.10.0 - ready yet?
Simon - thanks for the report
On 11/02/13 23:10, Simon Helsen wrote:
> 1) we had a few usages of org.openjena.atlas, but it was straightforward
> to adjust the package names. I am not anticipating significant effects
on
> our own clients since they should not
Steve, Rob, all,
OK - let's do it!
If we aim for 2 weeks of user community tests then see where we are.
(If we aren't getting reports there's little point waiting longer IMO.)
The formal release process takes 3-5 days.
The message to users@ is about to go ... if you have anything to add to
Simon - thanks for the report
On 11/02/13 23:10, Simon Helsen wrote:
1) we had a few usages of org.openjena.atlas, but it was straightforward
to adjust the package names. I am not anticipating significant effects on
our own clients since they should not be using these APIs. If they do, the
fix i
I think it looks pretty good.
I'm in about the same boat as Rob. We have a delivery in 3-4 weeks, so
would love to have a 2.10.0 by then.
-Steve
On Sunday, February 10, 2013, Andy Seaborne wrote:
> How are we doing for a Jena 2.10.0 release?
>
> I think we're ready to start pre-release testing
ents start to adopt, but at least
there is nothing major right now. Subtle corruption problems may also be
uncovered later on in the game. But I can only report on the ones I see
Simon
From:
Rob Vesse
To:
"dev@jena.apache.org" ,
Date:
02/11/2013 01:46 PM
Subject:
Re: Jena 2.10.0 -
Hey Andy
Personally I have been very happy with the stability of 2.10.0, bar the
minor hiccups with the streaming updates API getting finalized it has
caused us minimal problems and allowed us to eliminate workarounds for
some bugs we had previously encountered. QA have reported no regressions
or
On Mon, Feb 11, 2013 at 2:31 PM, Dave Reynolds wrote:
> On 10/02/13 19:12, Claude Warren wrote:
>
> I propose that we mark the following as deprecated with the noted
>>> substitution
>>>
>>> ArrayIterator : Arrays.asList( x[] ).iterator();
>>>
>>> ConcatenatedIterator : NiceIterator.andThen()
>>>
On 10/02/13 19:12, Claude Warren wrote:
I propose that we mark the following as deprecated with the noted substitution
ArrayIterator : Arrays.asList( x[] ).iterator();
ConcatenatedIterator : NiceIterator.andThen()
IteratorIterator : add a method to WrappedIterator to create an
ExtendedIterato
Done now -sorry about the noise.
There should be no warnings or output during initialization whether RIOT
initialization is via Jana, forced early by the application, or via the
ARQ test suite.
(The ARQ JMX support was not initializing in the right place - RIOT does
not need this to operate)
Sorry - still not stable enough. I've removed it until I can be certain
it's working properly.
Andy
On 10/02/13 19:42, Andy Seaborne wrote:
On 10/02/13 16:24, Andy Seaborne wrote:
IOT - jena is not automatically initializing RIOT readers into
model.read currently; it only happens if
On 10/02/13 16:24, Andy Seaborne wrote:
IOT - jena is not automatically initializing RIOT readers into
model.read currently; it only happens if ARQ initializes or RIOT.init is
explicitly called. May be doable for the release but I prefer to be
quite sure automatic initialization is stable for al
On Sun, Feb 10, 2013 at 7:10 PM, Claude Warren wrote:
> On Sun, Feb 10, 2013 at 6:17 PM, Andy Seaborne wrote:
>> On 10/02/13 16:59, Claude Warren wrote:
>>>
>>> I recently went through the iterator classes and think that there are
>>> some that should be removed because the base java classes now
On Sun, Feb 10, 2013 at 6:17 PM, Andy Seaborne wrote:
> On 10/02/13 16:59, Claude Warren wrote:
>>
>> I recently went through the iterator classes and think that there are
>> some that should be removed because the base java classes now support
>> the functionality (e.g. ArrayIterator) or are dup
On 10/02/13 16:59, Claude Warren wrote:
I recently went through the iterator classes and think that there are
some that should be removed because the base java classes now support
the functionality (e.g. ArrayIterator) or are duplicated elsewhere
(e.g. ConcatenatedIterator) Perhaps these should
I recently went through the iterator classes and think that there are
some that should be removed because the base java classes now support
the functionality (e.g. ArrayIterator) or are duplicated elsewhere
(e.g. ConcatenatedIterator) Perhaps these should be deprecated?
On Sun, Feb 10, 2013 at 4
How are we doing for a Jena 2.10.0 release?
I think we're ready to start pre-release testing with the user community
in advance of the formal release? This is not a purely incremental
release and it would be good to remove any unnecessary disruption that
the changes cause.
I have put some d
21 matches
Mail list logo
