tl;dr:
Let's release based on the current svn repo.
-------------------
There are 3 kinds of items to produce for a release:
1/ A "source-release" blob that firms the formal item to be voted on
(it's a maven artifact with classifier "source-release")
2/ Maven artifacts - the usual suspects.
3/ The download for use without maven
The RAT creates the "source-release" by taking a copy of svn at the
point of release. This state is also tagged in svn (e.g. maven release
plugin). The artifacts, including "source-release", are then deployed
to a staging repository and the votes can start.
The different parts of Jena are have different degrees of stability
which means, for now, releases of parts of the system will want to be
more frequently than others. Releasing everything too often means that
users of the stable parts (which is most of Jena) get a confusing message.
The RAT process for multi-module maven builds works if the project has a
single trunk, a POM in the trunk directory then a number of modules
including a parent. It does not work out-of-the-box with a layout of
trunk-per-module, which Jena has currently.
Long term, I think we should adopt that layout but, for now, I propose a
multiple build release with the current structure.
== What to release?
Proposal: JenaTop, IRI, Jena, ARQ, (?LARQ?) and a download.
That's 5 or 6 releases. :-(
But they are all the same pattern :-)
== Zip
To create a downloadable zip (and .tar.gz), I've put together an
artifact builder that takes it's dependencies (other Jena systems, and
their javadoc and sources), added in versions of the command line tools
that work with the download, to produce a single artifact.
I'd like to call that "apache-jena". The maven jars are called "jena-...".
e
The zip maker is also another Jena system and needs to be released. This
also gets round the fact that maven projects can only deploy one
artifact name, silently loosing or overwriting artifacts with different
names.
== Version number
I think it's worth bumping the minor version number on ARQ and Jena -
the jar files have changed name format; the maven artifacts have
different names, ARQ is SPARQL 1.1 (query, update) complete.
JenaTop 0
IRI 0.9.0
Jena 2.7.0
ARQ 2.9.0
LARQ?
Download 2.7.0 (in line with Jena core)
== Needed
Final clearing up:
A/ Remove doc/
B/ Turn off zip assemblies for IRI, Jena core and ARQ.
C/ test, fix, test, fix, test
D/ Write email announcements (I think we should hit the main semweb
lists this time round)
Then go for it. This should follow process of e.g.sling, except that
each system needs to be build-deployed-voted, not one thing. Not ideal,
it's 5 or 6 items, but it isn't actually much more work.
Of course, next time, it will be easier ...
== After
* Multi-module projects RAT-friendly layout [+]
* TDB
* Fuseki
Andy
