Maybe what is in master is enough?

Gary

On Tue, Oct 24, 2017 at 10:31 PM, Bruno P. Kinoshita <
brunodepau...@yahoo.com.br.invalid> wrote:

> Not so familiar, more familiar with Jena, but they are related.
> If nobody else volunteers, I can try to spend a weekend triaging issues
> and seeing if I can catch up with the changes since the last release and
> volunteer to cut a new release.
> CheersBruno
>
>       From: Gary Gregory <garydgreg...@gmail.com>
>  To: Commons Developers List <dev@commons.apache.org>
>  Sent: Wednesday, 25 October 2017 4:25 PM
>  Subject: Re: [RDF] Commons release?
>
> Hopefully someone who is familiar with Commons RDF is reading this...
>
> Gary
>
> On Fri, Oct 20, 2017 at 2:25 PM, Aaron Coburn <acob...@amherst.edu> wrote:
>
> > Hello,
> >
> > I wanted to check in on the status of a 0.4.0 release of Commons RDF. It
> > seems that all of the open PRs have been merged. Any idea on a timeframe
> > for the next release?
> >
> > Thanks,
> > Aaron
> >
> > On 9/19/17, 5:58 PM, "Aaron Coburn" <acob...@amherst.edu> wrote:
> >
> >    Sergio,
> >
> >    Thanks! The LDP server implementation is spread across quite a few
> > repositories in this github organization: https://github.com/trellis-ldp
> > (everything is Apache2 licensed), but the core abstractions are found in:
> >
> >    API: https://github.com/trellis-ldp/trellis-api
> >    SPI: https://github.com/trellis-ldp/trellis-spi
> >    HTTP layer: https://github.com/trellis-ldp/trellis-http
> >
> >    Most of the components have already been released to maven central,
> > but I'm still working on a few of them (particularly the HTTP layer and
> the
> > persistence layer).
> >
> >    The main difference between this and, say, Marmotta, is that this
> > implementation is designed to scale horizontally. And by making use of
> > Commons-RDF, the interfaces of this LDP server aren't tied to a
> particular
> > RDF library implementation -- e.g. Jena or RDF4J -- though I do use Jena
> in
> > the implementation code. I am also making significant use of ZooKeeper
> > (Curator), Kafka and Beam.
> >
> >    Aaron
> >
> >    > On Sep 19, 2017, at 5:27 PM, Sergio Fernández <wik...@apache.org>
> > wrote:
> >    >
> >    > Hi Aaron,
> >    >
> >    > you're right, we have quite some things to release. But first I' d
> > like to
> >    > take a look to our backlog, because we have some open PRs. Hopefully
> > I'll
> >    > have some time later this week, at the latest on the weekend.
> >    >
> >    > Just for curiosity, can you provide us a pointer to your Commons
> > RDF-based
> >    > LDP implementation?
> >    >
> >    > Thanks.
> >    >
> >    > Cheers,
> >    >
> >    >
> >    >
> >    > On Mon, Sep 18, 2017 at 2:24 PM, Aaron Coburn <acob...@amherst.edu>
> > wrote:
> >    >
> >    >> Hi!
> >    >>
> >    >> The last release of commons-rdf was from last November, and there
> > are some
> >    >> nice features in the master branch that I would really like to use
> > --
> >    >> especially the improved OSGi support. It seems that there are a few
> >    >> unresolved jira issues, such that this wouldn't be a 1.0 release,
> > but even
> >    >> a 0.4.0 release would be great.
> >    >>
> >    >> As a little background, over the last several months I've built a
> > server
> >    >> implementation of the W3C Linked Data Platform in which commons-rdf
> >    >> provides all of the core RDF abstractions.
> >    >>
> >    >> Would it be possible to move forward with a release? I would be
> > more than
> >    >> happy to help out.
> >    >>
> >    >> Thanks,
> >    >> Aaron
> >    >>
> >    >> acob...@apache.org
> >    >> ------------------------------------------------------------
> > ---------
> >    >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >    >> For additional commands, e-mail: dev-h...@commons.apache.org
> >    >>
> >    >>
> >
> >    ?B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
> > KKKKKKKKCB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��[[ۜ˘\?
> > X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��[[ۜ˘\?X�?K�ܙ�B
> >
> >
> >
>
>

Reply via email to