...
- Announcements
- 6.0.0 Beta Release
- Plan for Beta
- Target release date for 6.0.0
- Development
- core
- external utilities
- ?
- Testing
- Migrations
- Scalability/Performance : Performance Testing Criteria
- ?
- Life after 6.0.0
- Pilot Update
- PRs needing attention
- New Issues:
Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3655
- <Your topic here>Camel and Solr
Tickets
In Review
Expand Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 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 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 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
Notes
- Announcements
- David says that there's a lot of interest in Fedora 6.
- UC Davis is interested in F6
- Mike Ritter will be joining next week
- Sprint
- Review of the Board
- documentation review remaining
- solr and camel integration will be pushed back in later sprint
- rebuild speed issue Danny added in fix in code and merged
- Sprint going well
- What is the target for the final release? What tickets still need fixed? Where is the line?
- release planned for Monday next week
- Jira ticket 3640 review timestamp issue remaining, not a beta release blocker
- Review of the Board
- Questions/discussions:
- is
fcr:fixity
still considered deprecated?- There are some users who expect this functionality to exist
- Leave it till there's a viable replacement
- Something needs to be added to the spec
- Do we need F2 code in the migration utils?
- Unsure if the F2 code works or if anyone still uses F2
- Seems like it's okay to remove
- Ben wants to migrate the entire FOXML without splitting it up as part of a PLAIN_OCFL migration
- Ben will add PR to the feature
- Removing fcrepo-config.xml
- https://github.com/pwinckles/fcrepo4/commit/16205c9e0386048e5138c2cd402d55066170ed23
- Moving beans to Java Config and adding properties for configuring without touching spring
- Should be fine for most use cases. Unclear if people have custom auth configurations that may be more difficult for them to configure – still requires custom spring config
- is
- Performance Testing
- PRs
- The last sprint was very successful and Beta has arrived. The future is now.
- Upcoming user group meetings for Europe in March and North America in April.
- Post-Beta Plans
- Shooting for April to Release 6.0.0
- What to do other than obvious bug-fixes and community feedback?
- Test databases other than postgresql, specifically MySQL, esp 5.7
- Issue with 503 character limit for IDs is looming. Will need to reach out to see if it would affect anybody.
- Updating the camel-toolkit
- Drop OSGi and make spring boot jars
- Do we offer these seperately or make one box that you can configure to run only the services you need
- We'll set up a meeting to go over the strategy for moving off of Karaf and how best to provide that to the user
- Test databases other than postgresql, specifically MySQL, esp 5.7
- Ben C wants an switch build into migration util that does OCFL java validate datastream checksum compute that will be migrated comparing and validate with what is in foxml in fedora 3