Time/Place

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

Time: 11:00am Eastern Daylight Time US (UTC-4)
Dial-in Number: (712) 775-7035
- Participant Code: 479307#
- International numbers: Conference Call Information
- Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
IRC:
- Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #fcrepo on irc.freenode.net
- ? add slack channel info here?

Attendees

4.7.5 release testing - discussion of where things stand
Sign up for API Alignment sprints by adding your name
Delta Document, Sprint Optimization, and due dates
Compatibility Test Suite
Pairtree/Appletree options
1. Proposal (based on group discussion)
  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.
2. ```
As yet undecided
```
  1. ```
  when pair tree node creation is enabled should performing a GET or HEAD
```
  1. ```
  return non-pair tree children as they do now?
```
  2. ```
  return a 400 series message (404 or 405)?
```
2. ```
If both 1 and 2, what should the default behavior be? 
```
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
```
 - Also move forward with creation-side resolution?
```
External Content: Redirect or Proxy? on fedora-tech
1. (TBD only is appropriate people are on the line)
Java release schedule and compatibility planning
1. See http://blog.joda.org/2018/02/java-9-has-six-weeks-to-live.html

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.

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.

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.

Kevin Ford's issue has been resolved - was due to hardcoded config in the release artifact
Solr issues have been observed in testing
- Solr config is set to use autosoftcommit: 1000ms
- Some custom predicates do not get indexed
- Likely all is well

ACTION: Would be great if Aaron Birkland could perform API-X tests
ACTION: Jared Whiklo to test CLAW
ACTION: Andrew Woods to add build scripts to testing wiki
ACTION: Bethany Seeger to do some Vagrant testing
ACTION: Jared Whiklo suggesting update to fcrepo4-vagrant to reduce toolbox retries to 1 - Unable to locate Jira server for this macro. It may be due to Application Link configuration.
ACTION: Kevin Ford to retest items that have 's
ACTION: Joshua Westgard to test postgres
ACTION: Andrew Woods to reach out to Carrick Rogers re:RC testing
ACTION: Jared Whiklo to help with release on week of the Feb 12th

Proposal:
1. by default, minted identifiers should not have any pairtree structure
2. by supplying a system property, the current pairtree generation can be restored
3. retrieving the pairtree nodes should either a) require a second system property or b) not be supported at all
Peter Eichman is working on a document specifying behavior of container segmentation
There is concern about support for the "pairtree workaround" going into 5.0.0