Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:

Attendees 

Agenda

  1. Any news from Kevin Ford's issue from list

  2. Updates from Michael Durbin's optionally updating server managed triples work

    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Comments related to namespace corruption issues from fedora-tech

  4. Need upgrade utility for 4.7.3 release:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

    1. This utility is up-for-grabs, if someone is interested in moving it forward

  5. Approaches for restoring versions in the context of import/export
  6. ...

  7. Status of "in-flight" tickets

    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Ticket Summaries

  1. Please squash a bug!

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Tickets resolved this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Tickets created this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Minutes

Server managed triples update

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
  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.