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 slack chat. Anyone is welcome to join...here's the info:

Attendees 

  1. Danny Bernstein
  2. David Wilcox (star)
  3. Jared Whiklo 
  4. Peter Winckles 
  5. Calvin Xu 
  6. Daniel Lamb 
  7. Ben Pennell 
  8. Thomas Bernhart 
  9. Mike Ritter 

Agenda

  1. Announcements
    1. Reminder: European Fedora User Group : Migration Break Out:   
      1. Tuesday, March 16th 9am Eastern
      2. Register – Day 1: https://lyrasis.zoom.us/meeting/register/tJwkcuugqT0sGtRyfohKlOLn8_RBNlByjKLF
      3. Register – Day 2: https://lyrasis.zoom.us/meeting/register/tJwrd-qtqDouE9YT7DNSpM9ZdrB3JctARhJk
    2.  Fedora Camel Toolbox Meeting Tomorrow 12pm Eastern
  2. Pilots / Testing
  3. Objectives
    1. pre-release
      1. identify and resolve mysql bottlenecks and performance issues
      2. performance and scalability verification
      3. fcrepo-migration-validator
      4. minor bug fixes and improvements
        1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
        2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
        3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
        4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  
        5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. Peri-release:
      1. fcrepo-camel-toolbox face-lift
  4. Current Work
    1. fcrepo-migration-validator
    2. ?
  5. 5.x point release  needed?
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  
  6. Publish changes to Fedora API (ServerManaged Prefer header)
  7. <your topic>

Tickets

  1. In Review

    type key summary assignee reporter priority status resolution created updated due

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

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

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

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

Notes


Actions

  • No labels