...
Please squash a bug!
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets resolved this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets created this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
Minutes
Server managed triples update
- Esmé Cowles will add a review this afternoon
- Michael Durbin will fix the way the feature is toggled
Issue regarding mangle namespaces
- Seems confusing that it was introduced between 4.7.0 and 4.7.2
- Hydra doesn't have a standard sidecar cnd file to register namespaces, but some hydra apps do
- Turns out that the change was after 4.7.0
- It is posited that cnd changes like this are "breaking" commits
- there was lots of concern about whether we should remove 4.7.1 and 4.7.2 since they could cause corruption either now (for upgrades) or later when they upgrade.
- we need to reproduce the problem to identify the scenario in which it comes up
- What should go in the 4.7.3 release?
- reverting the CND stuff (pending identifying that as the problem)
- don't want to slow down the process with improvements, just get out a fix asap
- maybe include fun new features as part of 4.7.4 very soon after
- hash uri stuff
- relaxed properties
- all the non-breaking changes
- there was consensus that the migration tool for skolemized blank nodes is not a blocker
- Don't want to pull resources off of import/export, but this corruption issue seems like it is more important
- Andrew Woods could spend some time revering the commits and roll a release
- Aaron Birkland, seeing the critical importance of this feature volunteered to lend a hand
- volunteers will write up scenarios that should demonstrate the bug and can be used to verify that it's resolved in 4.7.3, Aaron Birkland and Andrew Woods will run through the scenarios
Import/Export versions
- the goal of exporting a resource (and it's version history) and have it import and appear identical is the guiding principle
- Ben Pennell has suggested an export format
- Should we import using the modeshape versioning capability or import some other way?
- There's some complexity in versioning and huge amounts of uncertainty in implementors of the spec