I would like to include jena-security in the distribution as it is sensitive to the Jena version. Adding it to the trunk would be my objective. If there are no issues I would like to do that for the 2.11 release. What legals need to be done? Technically (besides adding the code to the trunk as opposed to experimental) what needs to be done?
I will modify the pom to depend on apache-jena-libs. Claude On Fri, Aug 23, 2013 at 7:04 PM, Andy Seaborne <[email protected]> wrote: > We were discussing a release > > http://mail-archives.apache.**org/mod_mbox/jena-dev/201307.** > mbox/%3C51F8EEE7.4040109%**40apache.org%3E<http://mail-archives.apache.org/mod_mbox/jena-dev/201307.mbox/%3C51F8EEE7.4040109%40apache.org%3E> > > and then things seem to have got rather busy. > > I think we should try for a release even if everything isn't done, then > release again if necessary. There are some great new things already in the > pipeline. > > We have a number of things and I think this is worth bumping to 2.11. > > * New website > > * jena-text > * jena-jdbc > > I'm assuming that these are not in download, they are in trunk though, so > released via maven and it all forms part of one release vote. > > jena-text drags in Lucene which might be considered a bit big to put into > the distribution (not something that worries me that much). > > jena-jdbc: > Is there documentation? > (at least something an announcment can point to :-) > > And also: > > * jena-client > Include if ready, not blocking. > > * jena-security > > Not sure the roadmap is here. Claude - thoughts? > > It can be anything from in trunk, so part of the formal release if the > legals are done, to advertising and keeping as a SNAPSHOT for now but > version-fixed to 2.11.0. > > (ps you want to depend on apache-jena-libs, not apache-jena) > > Andy > > > > > > -- I like: Like Like - The likeliest place on the web<http://like-like.xenei.com> Identity: https://www.identify.nu/[email protected] LinkedIn: http://www.linkedin.com/in/claudewarren
