At this point master is jena3 and there is a jena2 branch.

What is the purpose of the Jena2 branch, are we intended to provide
ongoing maintenance and back porting of 3.x fixes for the 2.x branch?  Or
is it simply a convenient place for those who want to stick to Jena2 to
work from?

The jena2 is there to leave choices as long as possible.

1/ backing out jena3.

2/ (maybe) doing a 2.13.1 in parallel to 3.0.0

3/ We can put in a jena2 build in Jenkins.


4/ java7 / jena2
   java8 / jena3

(The transaction and COW-B+Trees are java8 which reminded me)

        Andy

Java7(oracle) - End of Public Updates - April 2015 (or revised to be later)

Reply via email to