Versions Compared

Old Version 1

changes.mady.by.user Danny Bernstein

Saved on

compared with

New Version Current

changes.mady.by.user Thomas Bernhart

Saved on

Key

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

...

  1. Announcements/Updates
  2. Planned Breaking Changes (standing topic)
  3. Alpha Release Announcement Logistics

    1. Fedora 6 Testing

      1. Release date: Monday, Nov 16th
      2. Top-level release documentation - Road to Fedora 6.0
      3. Focus this week: resolving documentation tickets:
        1. Jira
          serverLYRASIS JIRA
          serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
          keyFCREPO-3459
        2. Jira
          serverLYRASIS JIRA
          serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
          keyFCREPO-3512
        3. Jira
          serverLYRASIS JIRA
          serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
          keyFCREPO-3513
      4. Upgrade bugs
        1. Jira
          serverLYRASIS JIRA
          serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
          keyFCREPO-2983
        2. Jira
          serverLYRASIS JIRA
          serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
          keyFCREPO-2985
        3. Jira
          serverLYRASIS JIRA
          serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
          keyFCREPO-3521
        4. Jira
          serverLYRASIS JIRA
          serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
          keyFCREPO-3522
      5. After documentation and before next Monday, review/merge following tickets (note, none of these are Alpha blockers. Documentation is the priority):


        1. Expand

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


      6. Fedora 6 Feature Tracking
      Your topic here


      2. Expand
        title
      Tickets resolved this week...
      1. Fedora 6.0 open issues

        Jira
        server

      DuraSpace

      1. LYRASIS JIRA
        jqlQueryfilter=

      13111

      1. 15700
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


    3. Transitioning away from Travis-CI
      1. Buildkite
      2. Circle-CI
      3. GitLab
      4. GitHub Actions

      5. https://semaphoreci.com/pricing

      6. https://www.appveyor.com/

    4. Transitioning away from DockerHub
      1. Amazon ECR
      2. Quay.io

    5. ...


    Tickets

    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

    Announcements/Updates

    ...

    1. From Steering Committee. Revisiting membership model for Fedora. Funding has been an issue, but the volunteer "pay what you want" model has not been working. Trying to improve funding model, diversify streams and find other possible benefits for membership.
    2. Leaders/Committers discussion on Alpha/Beta release requirements. Functionality is there, but the documentation is definitely lacking in someways.

    ...

    1. There are 4 documentation tickets to be done. Peter Winckles and Jared Whiklo will move to work some of those tickets.
    2. Upgrade process is largely done, but requires releases.
    3. Would it be good to define a code freeze point where we stop adding new features and concentrate on cleaning up for alpha release?
    4. How do we release the alpha, are they actually version tagged with alpha. Also good to have an specific alpha docker tag to allow people to access it.

    ...

    1. feature completeness as defined by API compliance (at least as compliant as 5.x was), and the features we promised (primarily the search).
    2. Beta release of the migration tooling.
    3. Clear idea of OCFL extensions requirements from the OCFL spec editors to complete the extensions already in use.
    4. Documentation of breaking changes.
    5. Defining the performance testing criteria.
    6. Validation tooling to verify migration completeness.

    ...

    1. A test where we create an Archival Group with 10,000 members. Autoversioning is turned on and each member is created individually. - from Danny Bernstein
    2. Many members type test, we were able to return approximately 4 million direct children.
    3. Repository has 1,000,000 Archival Groups with binaries in them. How quickly can that content be served. Possible a comparison against a repository with a single AG. - from Ben Cail
    4. Some possible tests - from Ben Pennell
      1. impact of number of versions
        1. Incremental additions to an AG
        2. Touch updates to atomic resource
      2. Containment tests, many children
      3. Membership, many members
        1. Members generated by Direct vs Indirect container
        2. isMemberOf scenarios
      4. Update times for adding a member to container with many members, Direct vs Indirect
      5. Update times for adding a child to container with many child, is there degradation?
      6. Update types for object with many properties
        1. Retrieval times for object with many properties (streaming vs non-streaming serialize)
      7. comparison of commit time for autoversioning vs on demand
      8. Performance impact of commiting transactions with many changes
      9. Ingest of large files, ensure performance doesn’t degrade as files grow or cause OOM
      10. Throughput of many small files

    ...

    • No anouncments

    Planned Breaking Changes (standing topic)

    • No breaking changes to be discussed

    Alpha Release Logistics

    • Alpha Release scheduled for Monday, 16th
    • Beta release, once feature completeness has been reached → ideally after next months sprint
    • Andrew Woods : Are there any tickets/PRs that need to be resolved/merged before Monday?
      • see also agenda item 3.e
      • Jira
        serverLYRASIS JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-3530
         
      • Jira
        serverLYRASIS JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-3523
    • Documentation
      • description of Alpha release features
      • overview of features which will be in the Beta release
        • might be possible to resolve
          Jira
          serverLYRASIS JIRA
          serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
          keyFCREPO-3522
          (Migration of Fedora 5 repositories rooted at '/fcrepo' to Fedora 6") before Monday
      • discussion regarding breaking changes:
      • upgrading process is currently not straightforward → could be streamlined
    • Daniel Lamb : Doesn't expect any problems integrating Islandora with Fedora 6
    • David Wilcox : Trying to assemble a group of testers that would be willing to test integration of various Samvera applications with Fedora 6
      • ActiveFedora will not be migrated to Fedora 6
      • Valkyrie should be migrated to Fedora 6, but not all Samvera applications have been migrated to Valkyrie
      • testing will happen probably early next year with the beta release
      • migration scenario for Samvera is still unclear (migration-utils alone won't be enough)
    • Peter Winckles : Beta after next months sprint is probably optimistic; Andrew Woods agrees
    • Focus this week: resolving documentation tickets; links to artifacts will have to be added on Monday
    • Open tickets for Fedora 6:
      • some tickets will take a lot of time to resolve
    • Jira
      serverLYRASIS JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-3514
      should be resolved for Alpha

    Transitioning away from Travis-CI

    • Peter Winckles CircleCI → on their free plan only one buidl at the time can run
    • Thomas Bernhart BuildKite → need to setup your own runners for executing the builds

    Actions

    •  Danny Bernstein to ensure that a JIRA exists for scenario of transaction does not succeed completely, but rollback does succeed (see: 2020-08-13- Fedora Tech Meeting)
    •  Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-08-13- Fedora Tech Meeting)
    •  Who:  Clarify in documentation that multiple simultaneous writes to OCFL are not supported
    •  migration-utils - translating RELS-EXT/INT into RDF in Fedora 6: is the functionality there? If not, add it.
    •  Andrew Woods  will look into releasing jetty-console
      Jira
      serverLYRASIS JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-3530
    •  Peter Winckles will look into resolving
      Jira
      serverLYRASIS JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-3522
    •  David Wilcox will add remarks regarding Samvera beta testing to Road to Fedora 6.0
    •  Andrew Woods will look again at the upgrade documenation pages
    •  Danny Bernstein and Andrew Woods will go through open tickets and update priorities for Beta release