I am going by the state of JIRA and PRs to get a sense of what is ready
so please mark "resolved" any JIRA are done even if waiting for a
response from any OP. JIRA can be reopened. OP's can't always find
time at short notice.
Osma,
How are thing looking from your perspective?
The main focus of the 3.3.0 release is the lucene/solr/ElasticSearch
changes. We should set the timeline based on this work.
PR#227 is open but the comments seem to imply the changes are in.
JENA-1305 mentions documentation.
There is also JENA-1313 - how do feel about before/after 3.3.0 on this?
My preference is "release early, release often" not make JENA-1313 a
precondition unless it is nearly ready - the lucene switch and
ElasticSearch are valuable to get out.
Andy
On 05/04/17 15:25, Andy Seaborne wrote:
How are things looking for a 3.3.0 release?
A lot of good stuff has happened and the clock tick is approaching.
I'm offering to either be the release manager to help someone with it.
What will be the next version number?
Andy
Thoughts:
1/ Our regular releases are 3.x.0 and we reserve 3.x.1/2/3 for
out of cycle releases.
So next release is 3.4.0.
2/ Harmonise the version numbers. 3.x.0 for everything. Don't worry
that we then have "Fuseki1 3.x.0" and "Fuseki2 3.x.0".
This may remove a small point of friction in the release eventually (not
this release) which is having to not reply repeated to the before/after
version questions from the maven release plugin.
The last time I tried that (elsewhere) maven failed to update to the
next version properly and I ended up with a broken mess which is why I'm
not suggesting this second step this late in the cycle.
