On 27/05/2019 16:12, Marco Neumann wrote:
can you let us know what that entails on your end? is it primarily a matter
of managing branches on github?
Bandwidth! Better to do Europe-morning than later in the day.
We release from the master branch and, with the Jenkins jobs, should
always
can you let us know what that entails on your end? is it primarily a matter
of managing branches on github?
On Mon, May 27, 2019 at 3:42 PM Andy Seaborne wrote:
> OK then - I'll start on 3.12.0.
>
> On 20/05/2019 21:46, ajs6f wrote:
> > I'm fairly open this next week and the first week of June.
OK then - I'll start on 3.12.0.
On 20/05/2019 21:46, ajs6f wrote:
I'm fairly open this next week and the first week of June.
ajs6f
On May 19, 2019, at 8:55 AM, Andy Seaborne wrote:
Greg's GeoSPARQL implementation is ready. It's on a branch in git and
ready to merge - legal NOTICES are
I'm fairly open this next week and the first week of June.
ajs6f
> On May 19, 2019, at 8:55 AM, Andy Seaborne wrote:
>
> Greg's GeoSPARQL implementation is ready. It's on a branch in git and
> ready to merge - legal NOTICES are done as is disabling tests under Java11
> (boo, hiss) because of
Greg's GeoSPARQL implementation is ready. It's on a branch in git and
ready to merge - legal NOTICES are done as is disabling tests under Java11
(boo, hiss) because of the test failures due to tiny double
precision/string representation changes Java8 -> Java11.
So we can do Jena 3.12.0 with
