...
Notes
Announcements:
Samvera Dev Congress
- Dan participating
- Valkyrization and Fedora 6 (Sirenia)
- Working toward 100% tests passing
- Sirenia Testing (https://docs.google.com/spreadsheets/d/1cBmqnbwWvpKLPOehpKBzuPZo1W1dYo7Y/edit#gid=202333338)
- Sirenia (https://github.com/samvera/hyrax/blob/main/docker-compose-sirenia.yml)
- Fedora-related issue involving encoded slashes (hashes?)
- There is a configurable element in later versions of Tomcat to allow/disallow
- As of tomcat 10, the option to configure will be deprecated
- Dan will follow up with clarification once he meets with Samvera group
- Valkyrization and Fedora 6 (Sirenia)
Pop Up Topics
- ISLE question from Slack- fgs repo is the default name as far as gsearch is concerned
- Jared will send a follow up with suggestion to the Islandora mailing list
- Seems to be a problem between Fedora and GSearch
Committer Code Signing Key Process/Release Process Review
- Where should we put the keys because old process doesn’t work
- Would be good to keep them on a public key server
- Jared added links to the wiki, and as long as any of these are used Sonotype will allow
- Thomas’ suggestion is to create a separate Fedora signing key
- Need to add it to the wiki somewhere for now
- Organize a group call to do the release live (fcrepo core, camel toolbox, migration-utils)
- Can everyone commit to looking at it in advance of the actual release
- RC on the 15th for release on February 29th
- Use tech meeting time to work through the process
Tickets
3818 - just a collection of ideas to simplify the process. Will look at finding time to test processes and hopefully this will simplify the release process
3917 -
3912 - changed name in pipeline fir docker image rebuild but not for fcrepo rebuild itself?
- May be resolved by the simplification of the release process
- https://github.com/fcrepo/fcrepo/blob/main/.github/workflows/build.yml
- Fix that GitHub action to remove current tags and only build with the tag of whatever we choose
- Remove it from the docker repo also
- Here we use “latest + version” tag
- Building main in this, and main isn’t always the most recent release
- Maybe stick with maven naming convention? “Main” is the tag?
- Consideration to stop using “latest” tag entirely