Hi, On Tue, May 16, 2017 at 8:34 AM, Sergio Fernández <[email protected]> wrote: > > On Wed, May 10, 2017 at 11:08 AM, Sergio Fernández <[email protected]> > wrote: >> >> * MARMOTTA-534: Long-term issue nobody wanted to spend time. So I already >> started to work on this issue. I already solve the backend problem. Now >> I'mm trying to get ti solve int he fronted, too. I expect to submit a PR >> later this week. >> > > Pull request #28 fixes MARMOTTA-534: https://github. > com/apache/marmotta/pull/28 > > It'd be great if someone else could validate it. >
Despite no further feedback or testing, I've just merged PR #28 which should finally fix MARMOTTA-534. > * MARMOTTA-428: we have a PR by Aaron Coburn [5], pending to be reviewed >> by Rupert (our OSGi expert). I can't really say much about the patch, but >> so far LGTM. So if I don' t hear anything from Rupert in the next week, >> probably I' m going to merge the PR. >> > > Rupert, have you had time to check that pull request? > Rupert, have you had time to check PR #22 https://github.com/apache/marmotta/pull/22 ? It'd be great if we could target a first release candidate later in May or > early June. > Because next week I'd like to prepare a RC... Looking into our backlog https://s.apache.org/marmotta-3.4.0-open-issues currently I'm thinking to shift MARMOTTA-624 and MARMOTTA-623 to 3.5.0. What do others think? Cheers,
