You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Time/Place

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

Attendees 

Agenda

  1. Announcements
    1. 4.7.5 Release Process begins
  2. 4.7.5 release - Planning for week of January,15th 2018
    1. Release manager - Osman Din
    2. Volunteers
      1. Testers
        1. ?
      2. Someone to review 4.7.5 commit message for signs of missing documentation?
      3. Preparers of Module Release Candidates

    3. Resources:
      1. component release process tracker: https://docs.google.com/spreadsheets/d/1I_zTMxh2l2rf2wpafoTwhSTR5GZuEoaTcZmTKCI3xT4/edit#gid=1769378986
      2. Release Testing - 4.7.5
  3. Fedora API Test Suite... needing:
    1. Try the tool against an API implementation
    2. Code reviewing the tool... lots of low-hanging fruit
  4. Simple, synchronous query in Fedora
    1. What will it take to make this happen?
    2. Prior art
    3. Queries to support
      1. select ?s where {?s ?p ?o}
      2. select ?s where {?s <some-pred> ?o}
      3. select ?s where {?s <some-pred> <some-object>}
  5. Tickets requiring attention
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Bethany Seeger to review?
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Ralf Claussnitzer to explore?
    3. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Ben Pennell to explore?
    4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - on hold or close?
  6. 5.0.0 release
    1. API Alignment
    2. Pairtrees?
  7. Beyond 5.0.0 - Areas of improvement
    1. Persistence?
    2. Journaling?
    3. Simple, synchronous query?
  8. ...
  9. Tickets In-Review

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Ticket Summaries

  1. Please squash a bug!

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Tickets resolved this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Tickets created this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Minutes


  • No labels