Versions Compared

Key

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

...

  1. 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


  2. 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


  3. 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


Minutes

...

Bethany – Got tests passing and rebased.  Working on getting binary memento tests to pass.  Hope to have PR later today or tomorrow AM.  Proxy and Copy should be covered.  Versioning of external content:  Has this scenario been addressed?

...



...

  1. Work merged into ‘master’. Worked out separation of binary and description.  With one command you can create a binary version and that automatically creates a version of the description. And then you can independently version them.  Work is in a good place.

...

Danny – CTS is getting there.  Should be in a good place by EOD to fix currently breaking tests, or to at least investigate the issues, and then it should be clear where to layer in the additional elements of the specification.

...

  1. Danny  - https://jira.duraspace.org/browse/FCREPO-2275?filter=14401  Grab a ticket and let’s see  if we can get ‘er done.

  2. If above tickets were closed, we'd be in alignment with spec.

  3. BUT definitely more work to do on Documentation and CTS.

...

  1. 5.x Documentation Updates matrix
    1. Danny - Took every 5.x documentation page and set up a process around documentation review.  Seemed straightforward and less arduous than using Jira for this.  Put you name by a page and get crackin’.

    2. Kevin – If those who worked on specific elements of the API – fixity or versioning for example – could initially review the carried-over documentation that would be really helpful as those individuals will be most familiar with the new interaction patterns and/or API differences.

    3. Andrew – Perhaps if Peter and Mohammed could look at WebAC....

...

Jira
serverDuraSpace JIRA
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyFCREPO-2604

...

  1. Are we comfortable with messages emitted?

    1. TIME.  Noted we need to talk about this but discussion postponed.
  •  Danny Bernstein Create a ticket to check whether or not the fcrepo-camel-toolbox still works with 5.0.  Part of that ticket is to evaluate whether or not there are dependencies on the jms.* headers included in the messages generated by Fedora
  •  Bethany Seeger Create tickets to test versioning and redirect/proxy.
  •  Kevin Ford Ask community about /fcr:fixity endpoint.
  •  Danny Bernstein Inquire with leadership group (and broader community?) about prioritizing ecosystem tools for alignment with 5.0.