Page tree
Skip to end of metadata
Go to start of metadata

Time/Place

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

Attendees

  1. Danny Bernstein
  2. Peter Eichman
  3.  Jared Whiklo  
  4. Andrew Woods  
  5. Ben Pennell  
  6. David Wilcox (star)
  7. James Silas Creel  
  8. Jon Roby

Agenda

  1. Announcements

  2. Sprint 2
    1. Are we ready to release RC 1? 
      1. Remaining work

        1. Tickets

        2. CTS

  3. <your agenda item here>

  4. Please squash a bug!

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

  5. Tickets resolved this week:

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

  6. Tickets created this week:

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

Minutes

5.0 Release

  • Tickets
    • Several tickets in review
    • https://github.com/fcrepo/Fedora-API-Test-Suite/pull/260 - fairly large cleanup
    • FCREPO-1889 - Getting issue details... STATUS - still an outstanding issue, not critical to the release. Jared assigned, to be completed by Monday
    • FCREPO-2923 - Getting issue details... STATUS - Ben Pennell assigned, to be completed by Monday
    • Not all CTS tests passing yet
    • FCREPO-2784 - Getting issue details... STATUS - not critical to the release
    • FCREPO-2921 - Getting issue details... STATUS - ready to go, just needs another committer to approve
    • FCREPO-2892 - Getting issue details... STATUS - needs review
    • CTS: If the spec says an implementation should return a certain response to indicate that an optional feature is unsupported, and such a response is recorded, the CTS should skip the test
  • How do we feel about the release candidate?
    • Andrew: we should take a day to do some sanity testing before release (candidate release testing page)
    • Not doing a vagrant box for the RC
    • UMD plan to do camel toolbox and 5.0 release testing and report any issues
    • Java client: Decoupled from Camel toolbox but still useful for other purposes. Not a requirement for the release candidate
    • Goal: release 5.0 by end of next week
    • Do we have a release manager? Danny is willing.
    • What is our goal for the RC? Community/ModeShape implementation plus the CTS. 
      • Alternate implementations are related for the release of the specification but not a requirement for the 5.0 release
      • We should publish the HTML report of the CTS for 5.0, along with any from alternate implementations
      • CTS doesn't currently report on the version of the software it is run against. It would be good to make this am optional user-provided parameter
  • No labels