Agenda

4.7.4 release testing (4.7.4 JIRA tickets)
1. Release planned for Aug 1
2. Samvera and CLAW testing?
3. Backwards-compatibility testing?
  1. Likely a breaking change that should not be in the 4.7.4 release:
    Jira
    server DuraSpace JIRA
    serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
    key FCREPO-2393
Fedora alignment to API sprints
The divide between 4.7-maintenance and master branches
1. Commits that are in 4.7-maintenance and should be in master:
Working towards the next Import/Export release
1. Ben Pennell? Michael Durbin? any word on
  Jira
  server DuraSpace JIRA
  serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
  key FCREPO-2459
Adjusting the approach to serving /fcr:assets. (github-pr)
Now that the fcrepo-2508 is closed, any update on the related tickets:
1. Jira
  server DuraSpace JIRA
  serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
  key FCREPO-2516
  - likely resolved, waiting on feedback from Jose Blanco
...
Status of "in-flight" tickets

Expand
Jira
server DuraSpace JIRA
jqlQuery filter=13202
serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

...

Minutes

Release candidate went out earlier this week
Attendees encouraged to run through tests
There have been many big fixes and improvements that have gone into master but have not come out in a point release
4.7.4 makes these available in a backwards-compatible way
Need CLAW and Samvera tests
Consolidating Spring configuration could be a breaking change
- Need to pull this commit out and tag RC2
Need better backwards compatibility testing
- May involve existing data
- May require an integration environment , sandbox style
- We could automate the creation of resources in Fedora for this build process
- Spin up a release candidate and feed it an import package
- Provide recipes for different expectations/types of data

There is a delta between the current iomplemention of Fedora and the spec, which we need to close with these sprints
First sprint starts Sept. 11 for 2 weeks. Aaron Birkland will coordinate
Second sprint starts Sept. 26 for another 2 weeks
Interested folks are encouraged to sign up
We will also support/encourage other implementations to implement the spec. Need 2 or more to validate the spec

4 commits in 4.7-maintenance and should be in master
These are revert commits for breaking changes that messed up namespaces for existing implementations

One ticket still in review
Ben P is making good progress on version import, but we needn’t wait on this issue to cut a release
- We can always cut a new release when versioning import has been implemented
Call for volunteers to do the release
- Danny B volunteered
- Jared will help