Time/Place

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

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Audio/Video Conference Link: https://lyrasis.zoom.us/j/396037251
  
  • Meeting ID: 396 037 251
  • Find your local number: https://lyrasis.zoom.us/u/ad6Xb7q3ia

  • Join fedora-project.slack.com on the "tech" channel

  • Self-register at: http://slack.fcrepo.org/

Attendees 

1. Danny Bernstein
2. David Wilcox 
3. Jared Whiklo 
4. Peter Winckles 
5. Daniel Lamb  
6. Ben Pennell
7. Calvin Xu 
8. Michael Ritter

Agenda

1. Announcements
   
   1. Release Party Date and Time
   2. Vacation reminders
   3. Steering update
2. fcrepo-java-client  release
3. Import Export PR needs a review: https://github.com/fcrepo-exts/fcrepo-import-export/pull/162
4. New tickets
   1. https://fedora-repository.atlassian.net/browse/FCREPO-3743 :  write directly to S3 in f4/5→ 6 migration
   2. https://fedora-repository.atlassian.net/browse/FCREPO-3741: updating a binary resource via the web console fails
5. Urgent release related issues?
6. Low hanging tickets  Fedora for  some  light  summer  coding:
   1. https://fedora-repository.atlassian.net/browse/FCREPO-3295: Return Link header indicating the AG of a resource (if applicable)
   2. https://fedora-repository.atlassian.net/browse/FCREPO-3286:  Malformed linked header gives NPE
   3. https://fedora-repository.atlassian.net/browse/FCREPO-3146:  remove deprecated methods (housekeeping)
   4. https://fedora-repository.atlassian.net/browse/FCREPO-3356: Improve duplicate key exception
7. Tickets to be prioritized: https://fedora-repository.atlassian.net/issues/?filter=1001
8. Your topic

Tickets

1. In Review

   Click here to expand...

   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!

   Click here to expand...

   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:

   Click here to expand...

   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:

   Click here to expand...

   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