It would be nice to make a release now we are out of incubation.
I think doing the least to make the release happen is the right next
step but I can be persuaded that doing more on integration of components
is worth waiting for.
Starting proposal:
1/ Single source release, not one per module.
2/ Two downloads:
apache-jena being iri-core-arq-tdb
jena-fuseki being Fuseki
(==> switch off assemblies for ARQ and TDB for the release)
3/ Separate versions numbers for component, numbering as we have in svn
at the moment
. we haven't experimented with an uber jar yet
shouldn't be any problems other than verbosity of the plugin
. separate jars mean we can release updates
for example, fine-tuning for final SPARQL stuff.
4/ The parent is not a separate release.
If we do a single build, I can't think of a reason
for a separate parent but I may have missed something.
Thoughts?
Any JIRA that you feel a strong need to complete and get in the next
release?
Paolo - what about LARQ? If it gets placed in the release, would that
hamper getting incremental update released soon? Or do as a parallel
release (i.e. not in apache-jena but part of the build) to get the
version moved on to non-incubating.
Next step:
I will set up a Jenkins job to build (2.7.1-snapshot) apache-jena as a
preliminary step and then disable the explicit snapshot builds of
iri-core-arq-tdb.
We can inspect the binary it builds ... and it will at least mean no
ordering problems with snapshot builds.
Andy
PS And no more icu4j!
