Fedora Dependency Upgrade Project

[Arran Griffith]

Hi Everyone,

I hope you had a nice weekend. Yesterday, we kicked off a large-scale technical project to update the dependency libraries contained within fcrepo-core. This work focuses on modernizing Fedora’s core codebase, and bringing it up to modern, current versions of all out-dated dependency libraries. Work will commence by first evaluating and improving test coverage to ensure a smooth rollout and streamline future development and maintenance, then upgrading critical dependencies, to current, supported versions. Read about our Dependency Upgrade Project here.

 

See the Dependency Upgrade Project on GitHub.

 

Overall Project Goals
Expand code test coverage to:

• Enable a streamlined, automated upgrade strategy
• Improve code robustness and maintainability
• Facilitate community contributions and faster development

 

Upgrade Fedora’s core dependencies to the latest versions.

 

Phase 1: Code Coverage Review

Expanding code test coverage is a prerequisite to starting the upgrades. We will lay the groundwork for expansion of test coverage by:

1. Adding an automated code coverage tool (CodeCov) to the targeted Fedora repository. ✅ Completed
2. Upgrading to the latest version of the core unit test framework (Junit 5) ✅ Completed
3. Assessing the gaps in coverage, and prioritizing those modules that will be most impacted by the dependency upgrades. 
4. Writing and integrating new tests for any/all modules not meeting the 80% coverage minimum standard.

 

Code Coverage Review work is outlined in the "Part 1: Code Review" tab within the project on GitHub.

 

We Need YOU!

We are reaching out to the entire community of Fedora users to help with this effort. We need individuals with experience in code coverage review as well as anyone with experience writing unit and integration tests! All levels are welcome and encouraged to participate. This is the perfect opportunity to get started with contributions to the Fedora community. 

 

To participate in the code coverage review:

• Find the “Part 1: Test Coverage” tab on the Fedora Dependency Upgrade Project GitHub board.
• Review Jira issues labelled "Ready" and assign issues of interest to yourself to indicate you are working on it.
• Fork the code to begin your work.
• Change the status to "In Progress" to indicate work has started.
• Please write tests for the high priority gaps, providing any relevant comments into the Jira Issue if necessary.
• Once complete, submit a pull request with your work and change the ticket into "In Review".

 

We will be working in 2-week sprint-style focused working blocks to accomplish the code coverage review. The first block of work runs from March 31 - April 12, 2025. Check-ins will happen during the regular scheduled Tech Meeting - every Thursday @ 11am Eastern.

If you are new to the Fedora project, please see our Guide for New Developers to get started.
If you have any questions, please reach out to the Fedora Team via email (fed...@lyrasis.org) or join us on Slack (https://fedora-project.slack.com/).

 

Looking forward to seeing your work in the project!

Cheers,

Arran

---

Arran Griffith

Program Manager, Fedora Program

Lyrasis