Hi all, I did some (mostly automatic) code cleanups across the Marmotta source tree as a preparation. Caught a couple of bugs on the way, not sure how much impact they had before.
What's the timeline for releasing 3.4.0? Any missing features? Sebastian Sebastian Schaffert <[email protected]> schrieb am Mi., 9. Nov. 2016 um 20:21 Uhr: > Hi Sergio, > > Thanks for pushing this forward. I can do something next weekend (in 10 > days). I am anyways oncall and need to stay at the computer. > > Cheers > > Sebastian > > Mark A. Matienzo <[email protected]> schrieb am Mi., 9. Nov. 2016, > 17:37: > > Hi all, > > I've got limited time to contribute patches directly but I'd be happy to > assist with code review. > > --mark > > -- > Mark A. Matienzo <[email protected]> | http://anarchivi.st/ > > On Wed, Nov 9, 2016 at 6:44 AM, Jakob Frank <[email protected]> > wrote: > > > Thanks Sergio for bringing this up - a release is indeed long overdue! > > > > * MARMOTTA-534 is something annoying that is with us for too long > > > > > This login-form issue is really annoying - thanks to @thomas who > > volunteered to take care of it! > > > > > > > * We have some KiWi issues (MARMOTTA-640, MARMOTTA-651, MARMOTTA-652) > we > > > should fix. > > > > > I fear these are really tricky. Diving into the SPARQL to SQL translation > > requires quite some effort... > > > > > > > * I shifted MARMOTTA-584 to 3.5.0 since it introduces a db schema > change > > we > > > can't support in all databases, therefore requires major work. > > > > > +1 > > > > > > > * I'd see we should also shift the Sesame upgrade (MARMOTTA-635) > > > > > +1 - i fear upgrading sesame (or even switch to rdf4j) will cause major > > disruptions in the code, especially when it comes to the test-suites... > > > > Let's see if we can make some progress towards 3.4.0, > > best, > > Jakob > > -- > > Jakob Frank > > | http://redlink.co > > | m: +43 699 10588742 <+43%20699%2010588742> | e: [email protected] > > | http://at.linkedin.com/in/jakobfrank > > > >
