Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Task marked complete

...

Agenda

  1. 4.7.0 release candidate - testing and migration
    1. Backup/Restore issues
  2. 4.6.1 release - patch for concurrent resource creation
  3. Semantic versioning, API Specifications and releases post-4.7.0
  4. new fcrepo-vocabulary repository?
  5. API Specification - Taking it to the streets
  6. Move Yinlin's tests into fcrepo4-labs
  7. Status of "in-flight" tickets

    Expand

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

...

  1. The process seems to be going well.
    1. ActiveFedora issue does not seem to be a blocker.  Ideally Drew can provide feedback before we turn the crank.
  2. Release schedule: Halloween? Let's plan for early-ish on Monday after talking to Drew and Stephano.
    •  Jared Whiklo is concerned that we haven't  the data migration enough - will touch base with Drew
    •  Andrew Woods will circle up with Stephano Stefano and the gang about migration
    •  Andrew Woods will check with Drew Stefano that all is well with   Michael Durbin's 4.6.1 patch  before dropping the monkey.

...

There are two factors that define require a major release:

  1. breaking changes to the API
  2. required backend data migration

...

  • A robust test suite should be part of that milestone.


new fcrepo-vocabulary repository

  • reduces potential for misspellings
  • uses RDF commons  - a level of abstraction above Jena.
  • in labs right now
  • should wait to merge into core until after the next version (0.3) of that alignmentRDF commons comes out.
  • increases reusability
  • Unknown User (acoburn)  :  would like to keep the included ontologies to what is being used in the code.

API Specification - Taking it to the streets

A. Soroka has institutional support to move the process forward.  He is working to get the API (starting with the core) to the point where we can put it out to the wider community for feedback.

Perhaps we need a document that shows the delta between  the reference implementation and the API  today.  We could use this to track our progress towards 5.x.  Non-Adam's could help on this.

Aisha: Maybe consider looking at https://apiblueprint.org/..

 

Move Yinlin's tests into fcrepo4-labs

...

 

Moving FCREPO-2105 forward

  • Unknown User (acoburn)  will work on wrapping Guava-based converter implementations with new Java 8 functions
  • Danny Bernstein will then  revisit each converter in order to  factor out Guava and implement performance related improvements where applicable.