So we are including (another [1]) mayor change "last minute" into the upcoming release [2]?
Did anyone check these changes (MARMOTTA-418 and [1]) with the downstream projects? For the future, I think it would be great to discuss such changes in advance! Best, Jakob [1] http://mail-archives.apache.org/mod_mbox/marmotta-commits/201401.mbox/%3Ca550fc7a856843ef847ceeb3a77312a1%40git.apache.org%3E [2] (This time, at least, we have an jira issue) On 10 January 2014 23:10, ASF subversion and git services (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/MARMOTTA-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868381#comment-13868381 > ] > > ASF subversion and git services commented on MARMOTTA-418: > ---------------------------------------------------------- > > Commit f282e64b4462f905850c2674ac3079a61bdbbd0e in branch refs/heads/develop > from [~wastl] > [ https://git-wip-us.apache.org/repos/asf?p=marmotta.git;h=f282e64 ] > > MARMOTTA-418: fix cache filter > > >> Improve LDCache API >> ------------------- >> >> Key: MARMOTTA-418 >> URL: https://issues.apache.org/jira/browse/MARMOTTA-418 >> Project: Marmotta >> Issue Type: Improvement >> Components: LDCache >> Reporter: Sebastian Schaffert >> Assignee: Sebastian Schaffert >> Fix For: 3.2 >> >> >> The LDCache API is currently very difficult to understand. It should be >> simplified so that users only need to call straightforward methods like >> - ldcache.get(resource) >> - ldcache.refresh(resource) >> - ldcache.expire(resource) >> This is a major (breaking) change of the API as well as the backends and we >> need to make sure all existing implementations keep their functionality. > > > > -- > This message was sent by Atlassian JIRA > (v6.1.5#6160)
