On 07/04/17 11:30, Osma Suominen wrote:
06.04.2017, 19:21, Andy Seaborne kirjoitti:
Osma,
How are thing looking from your perspective?
Looking pretty good for a release, however, the documentation updates
are not yet done. I was hoping Anuj would do an update but he hasn't
responded...
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.
It can be closed, I just don't have the rights to do that. I put in a
comment stating the same.
Not through the GH UI but we want to put it into the ASF copy which gets
mirrored to GH, not update the GH mirror and flow back to ASF..
Any commit on the ASF codebase with the magic phrase will do. It does
not have to the only comment or indeed on the first line. As the phrase
is quite bland, it's a bit scare really.
It can be done after all the work with:
git commit --allow-empty -m "JENA-1305. This closes #227."
Normally, this can be done within the workflow of pulling from GH
git pull github pull/227/head --no-ff
... editor pops up with the merge message ...
... add a line saying ....
"JENA-1305. This closes #227."
...
where:
[remote "github"]
url = [email protected]:apache/jena.git
fetch = +refs/heads/*:refs/remotes/github/*
this ought to be written down on
https://cwiki.apache.org/confluence/display/JENA/Processes
now that we use this if anyone has a moment to start some words.
The GH flow is working well and I think it encourages contributions. The
fact we use it as well as contributors outside the PMC is important.
JENA-1305 mentions documentation.
Right. That should be done by the time of release, or soon after. I'll
make sure that it gets done one way or other.
There is also JENA-1313 - how do feel about before/after 3.3.0 on this?
No reason to delay the release because of a proposed new feature for
which we don't yet have any code.
OK.
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.
Agree.
-Osma
Thanks for the update ... onward to 3.3.0.
Andy
