On 26/01/15 19:11, Rob Vesse wrote:
Comments inline:
On 24/01/2015 10:28, "Andy Seaborne" <[email protected]> wrote:
== Jena 2.*
Some first thoughts for the next release ...
What number should it be? We may have have new components:
* OSGi bundle
Yes assuming Stian has something that is sufficiently workable
* Adds Fuseki2 (as 2.0.0); Fuseki1 still there
* jena-elephas?
(If this works for you, Rob - no strong advocacy either way)
Yes I would like to get this out, two things to be aware of:
- Do we add a -beta to the Maven version (I think Fuseki 2 does this
currently?)
Fuseki is now 2.0.0 (no beta). I flipped it recently because there has
been feedback (thanks Trevor!). It's not like it is frozen in stone and
Fuseki1 is still around so it's a gradual migration anyway.
I can be pursuaded otherwise.
For jena-elephas it's new, so it isn't undoing any users existing
investment. I'm not a fan of the "1.0.0 is perfect" or the "perfect
only releases" but see "release early, release often" at the Jena scale
as about incremental versions.
Now - if this were httpd, or tomcat, things would be different.
My mental test is "is it better than before?"
- JENA-821 is still an issue but there is a known workaround described in
the documentation so I think that is OK
I will go ahead and get this merged into master (prepare for giant email
deluge on [email protected])
* Anything else I've forgotten.
Could people please review the following JIRA filter:
http://s.apache.org/jena-no-fix-version
This lists all resolved Jena issues that don't have a Fix Version set, I'm
not expecting people to go back and retroactively change all ~200 or so
issues but certainly those that have been fixed in the last couple of
months could you please Reopen, update the Fix Version field appropriately
and then Close again.
Good idea.
We might be able to do with three bulk changes of the JIRA : open,
update, close if the process does not loose the grouping. I may try it
(on a bulk update of one).
If so, maybe the best way is to find a cut off point (2.12.0?) and set
that for all that closed before that release date (2nd August 2014)
"Are you feeling lucky?"
We don't have to do one release so if timing works better for new
components, we can do 2.13.x , 2.14.x, to indicate new modules.
2.13.0 would be a good idea given the number of new components involved
Agreed.
Rob
Personal opinion: If it gets too complicated or too lockstep,, then we
should split to do a 2.13.0 real-soon-now and then do 2.14.0 fairly soon
afterwards. Numbers are not in limited supply.
2.12.1 was early Oct so we are still well within our target of 6 month
releases.
== Jena3
Very soon after 2.12.2 or 2.12.3, kick off Jena3.
I'll start another thread for Jena3 process and use this thread for 2.x
releases.
Andy
