Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. In Review

    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=13100
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  2. Please squash a bug!

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13122
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  3. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  4. Tickets created this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13029
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


Notes

  1. Announcements
    1. Jira 3281 - project infrastructure. Issues between CLI, Eclipse, & IntelliJ. Peter to investigate.
    2. Jira 3291 - travis deploy?
  2. Open PRs
    1. 1669 - patch. Integration tests work now. Code is simpler now. Andrew to review.
    2. 1667 - containment relationships weren't persisted, but now they are.
      1. Jared to make a ticket about rebuilding if DB goes away.
  3. May sprint
    1. simple search
    2. plain vanilla objects
  4. JMS
  5. Fedora 6 testing
  6. Containment index
  7. housekeeping PRs
  8. Fedora 6 Roadmap

Actions

  •  Danny Bernstein to ensure that a JIRA exists for scenario of transaction does not succeed completely, but rollback does succeed (see: 2020-04-30 - Fedora Tech Meeting)
  •  Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-04-30 - Fedora Tech Meeting)
  •  Who:  Clarify in documentation that multiple simultaneous writes to OCFL are not supported
  •   Who:  After team has a chance to comment, send Ghost Node idea to general community for feedback
  •   Who: Decide who works on what in the next sprint

...