btw, my patch in 131 can be applied and run. That seems pretty reproducible to me. You won't get the index out of bounds of course since that is only a consequence. Please apply the recommended change. It proves the Transaction code has a problem
thanks Simon From: Paolo Castagna <[email protected]> To: [email protected] Date: 11/04/2011 10:17 AM Subject: Re: What are the JIRA issues to fix before a release? Simon Helsen wrote: > I would like to see both > > https://issues.apache.org/jira/browse/JENA-131 > https://issues.apache.org/jira/browse/JENA-143 > > resolved > > I provided input for 131 - I still have to try to produce a test-case for > 143, but depending on the origin of 131, it may be connected to the > problem in 143 Hi Simon One option in relation to JENA-131 and JENA-143, since they do not have a test case we can use to reproduce the problem at the moment, we could decide to release TDB anyway and, as soon as the bug becomes reproducible, we fix it and we can release a bug fix release x.y.(z+1). Another option is: we release all the Jena modules but TDB. For TDB we produce a candidate release and wait a little bit more to push that out to see if we can reproduce the problem (and fix it). However, in this case Fuseki (and LARQ) will also be impacted. This way, neither JENA-131 or JENA-143 would be blockers for our first Apache Jena release. I would not propose this normally and absolutely not if there were an open bug with a test case to reliably reproduce it. Any help in writing a test case to reproduce the problem is certainly appreciated. Thanks again for your feedback on JENA-131 and JENA-143. Paolo > > thanks > > Simon > > > > > From: > Paolo Castagna <[email protected]> > To: > [email protected] > Date: > 11/04/2011 09:21 AM > Subject: > What are the JIRA issues to fix before a release? > > > > Hi, > today, I have time to work on Jena. > > What are the JIRA issues to fix before a release? > > Paolo > > > >
