Andy Seaborne wrote: > On 30/11/11 13:31, Paolo Castagna wrote: >> Andy Seaborne wrote: > >>> == After >>> >>> * TDB >>> * Fuseki >> >> Yes, please. > > TDB as two outstanding blocking JIRA (163 and 102).
Ack. JENA-163 is still a 'mystery' to me. I followed your comments and changes, but I do not understand where the root cause of the bug is. We had problems with .truncate() in the past and I went to check if that was related, but I did not find anything 'interesting'. JENA-102 is important, but less mysterious. > Hopefully, after getting the release started, I'll be able to return to > those. > >> For TDB, even just a release candidate in the Apache Maven staging >> repository would help > > A staging release will have a weird, unstable URL (and a scary button > that if you press irreversible things happen). Ack. > The nightly build does at least have a stable URL. The nightly build is great and I use it when I develop (so that I can stay up-to-date and identify eventual (and very rare) 'incompatible' changes and fix them as soon as they happen, one at the time... rather than all together at release time or version upgrade time). This works very well for me. But, the nightly build has -SNAPSHOT in it. Therefore I cannot use the Maven release plugin to release internal projects if they depend on TDB. This is not a big issue, but I need to maintain a fork of TDB and roll out internal releases of it. This will not be a problem anymore as soon as a release of TDB with the transactional stuff in it is out. ( I am sharing this for the benefit of others and as information. I am not asking or expecting you or anyone to take any action on this. ) > >> (=> no need to fork and roll-out releases >> internally/elsewhere). Via Maven release plugin this should just a >> matter of type: >> >> mvn -Papache-release release:prepare >> mvn -Papache-release release:perform >> >> I've never tested this on the Apache infrastructure, > > I have, at least in part :-) Good. I did not try since I was not sure if there are non reversible side effects. > >> but I am using >> the Maven release plugin elsewhere with no problems. It's does a good >> job in automating the all process. The only problem is when something >> goes wrong, sometimes I need to rollback changes manually, but it's >> very rare. >> >> Paolo > Thanks Andy for pushing forward towards a release. Paolo
