...

1. Danny Bernstein
2. Andrew Woods - out
3. Aaron Birkland 
4. Bethany Seeger 
5. Ben Pennell 
6. Jared Whiklo 
7. James Silas Creel 
8. Yinlin Chen
9. Peter Eichman
10. David Wilcox
11. Jon Roby

Agenda

1. Announcements

2. 5.0.2:
   

   1. Release manager: Yinlin Chen

   2. Date: February 6th

   3. Release Testing - 5.0.2

3. Ecosystem release/development policy review

4. Status on current tools:
   1. fcrepo-camel and fcrepo-camel-toolbox toolbox release
      1. 4.7.3 release? (compatible with Fedora 4.7.x)
   2. fcrepo4-vagrant 
   3. fcrepo4-docker
      1. Please review this PR: https://github.com/fcrepo4-labs/fcrepo4-docker/pull/35
5. Next steps for import/export/4→5 migration
   1. Proposal: Two pronged attack
      
      1. round-tripping 5.x data (add support for versions and webacs)
      2. fcrepo-migrate:   transform 4.7 export into 5.x export
   2. A starting list of Jiras

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2979

      2. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2980

      3. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2981

      4. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2982

      5. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2983

      6. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2984

      7. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2985

6. 5.1.0 1.0
   1. Ready for review
      

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1889

      2. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2937

      3. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2936

      4. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2935

      5. "Check if metadata is available in commons.js" : https://github.com/fcrepo4/fcrepo4/pull/1499
   2. Issues that are ready to be worked:
      

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2976

7. <your issue here>

8. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

9. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

10. Tickets created this week:

    Expand
    Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

    
    

Minutes

1. Lyrasis and Duraspace are moving forward with an intent to merge process. There is some due diligence to be completed first. The merger in worst case will have no impact on the Fedora project, but in the best case Lyrasis has expressed an interest in investing resources in the Fedora project. There are opportunities for feedback if you or your organization have any available in the FAQ of the news release.
2. Travis-ci has been purchased by Idera (https://blog.travis-ci.com/2019-01-23-travis-ci-joins-idera-inc), should not have an impact but we might want to consider reviewing other options. (ie. Circle-ci)
3. Yinlin has volunteered to be the manager for the 5.0.2 bug fix release. Still waiting on work for the c3p0 replacement. Possibly announce a release next Monday. No movement on the c3p0 for a new release, perhaps we should move to apache-dbcp for a more robust product.
   Missing the jackson-bind fix on the master branch, it is on the 5.0-maintenance branch. Need PRs on the 4.7-maintenance and master branch.
   A pending PR (https://github.com/fcrepo4/fcrepo4/pull/1399) which updates a variety of dependencies should have a CLA, we have not heard from the author but as this is just updating version numbers then we can take this as a one-time occurence. We would need to indicate in the CLA table.
4. For a 4.7.6 release we also update the modeshape version in 4.7 to match 5 which includes the S3 fixes.
   A 4.7.6 release should occur ASAP and have more robust updates.
5. Fcrepo-camel and camel-toolbox seem they are ready to go. Peter was able to drop in these two products in their test environment and it worked mostly.
   fcrepo-camel or camel-toobox has a reference to the 4.7 pom file as parent. Updating this to anything later than 4.7 makes Karaf un-happy. It throws an Invocation target exception when PAX exam was trying to launch Karaf. Perhaps let Karaf fail and work backwards.
   Would also like to make the fcrepo-camel-toolbox support 4.7 messages.
   Will we have a maintenance branch of the fcrepo-camel-toolbox to support the 4.7 messaging?
   We have tagged versions of fcrepo-camel that work with 4.7.x but all development will be working with 5.0.x+
   Fcrepo-camel and fcrepo-camel-toolbox have security updates that need to be fixed.
6. API-tests for number of messages expected. We can switch == to >= and then look at a way for the user to specify an expected number of messages.

Actions

1. Announcements
   Nothing in particular
2. 5.0.2
   Off to the races!  Yinlin has taken role of release manager.
3. Ecosystem release/development policy review
   Yinlin had asked about the fcrepo4/docker project in the context of policies on merging PRs.  There’s no official policy on the labs repositories unlike the extensions or main repositories.  This is justifiable since there’s no guarantee of support for labs repositories’ code. But naturally, people can/should request reviews of PRs as a best practice.
4. Status on current tools 
   fcrepo-camel and fcrepo-camel-toolbox: the latter has some commits to master intended for release 4.7.3 that Peter’s using locally.  He asks what the RC policy should be there.  Daniel recommends an evaluation period for the toolbox since it is widely used.  A maintenance branch should be created, an RC tag cut, and a RC announcement should be made, but there’s no need for a wiki page, etc.
   Jared suggests that the maintenance branch may be superfluous as there are unlikely to be additional PRs in the interim. The evaluation period will be 1 week.
   There’s a problem building both camel and camel-toolbox with how they reference the parent pom.  Danny Bernstein will explore updates to fcrepo-camel-tests to resolve PAX Exam issue.
5. Next steps for import/export 4->5 migration
   Daniel’s feeling is that we’re not far away from being able to do this migration.  Two parallel tacks can be pursued.  We can focus on round-tripping 5.x data (exporting version, exporting webacs, and importing versions).  Also, create a new tool that would transform a 4.7 export to a 5 export.  
   It seems reasonable that we’ll make people upgrade to an appropriate version of 4.x before attempting the migration to 5.
   Consensus is that this approach is sound. Documentation will indicate the versions for the export and the import, and wiring in a migration tool at that point will be straightforward.
   Aaron points out that migrating the webacs could be the tricky part, since if there are containment relations between them, these will need to go away, and if there are out-links from any resources to the webacs that are not of the “this is my webac” variety, these will need to be eliminated.
6. 5.1.0
   Item 6.a.v is of questionable value as it’s for a rather customized case – it’ failing tests, but if the PR authors can fix that, it will all be good.

 

 

Actions

•  
•  Danny Bernstein dig in on camel toolbox friday to see what happens if runs Aaron's fcrepo-camel changes through it
•  Peter Eichman  is planning to work on documenting UMD's fixity check system on the  Fedora in Production: Case Studies wiki page.
•  Bethany Seeger will take a look at  Danny Bernsteinto create a JIRA around the problems update the parent past 4.7 and test updating https://github.com/fcrepo4-exts/fcrepo/Fedora-API-Test-Suite/issues/319
•  Danny Bernstein to create a PR on master and 4.7-maintenance for the jackson-bind security update.
•  Aaron Birkland to create a JIRA around the problems update the parent past 4.7
•  Jared Whiklo  to look into migrating from c3p0 to commons-dbcp in preparation for 5.0.2
• camel-tests
•  Peter Eichman  will take charge of the fcrepo-camel/fcrepo-camel-toolbox release process.
•  Jared Whiklo  will rebase the PR for 

  Jira
  server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1889

   and make sure Andrew Woods's and Peter Eichman's concerns are addressed.
•  Peter Eichman :  will complete review of 

  Jira
  server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1889

   when Jared Whiklo  is finished with the above.
•  Danny Bernstein  will test  Ben Pennell 's version import PR  for 4.7.5