Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

Developers Meeting on Thurs, Aug 22, 2024

Time/Location

 from 14:00-15:00 UTC

Location: https://lyrasis.zoom.us/my/dspace?pwd=RTk4QUhISnhPRi9YenVrTFJKbDllQT09 (Meeting ID: 502 527 3040).  Passcode: dspace

No meeting on Thurs, August 15, 2024

Tim Donohue  will be out of the office from August 12-20, returning on Weds, August 21.  Therefore, no developer meeting will be held on Thus, August 15.  The next meeting will be on Thurs, August 22.

Agenda

Attendees

Current Work

Project Boards

To quickly find PRs assigned to you for review, visit https://github.com/pulls/review-requested  (This is also available in the GitHub header under "Pull Requests → Review Requests")

Goals for 9.0

To be decided by DSpace Steering Group with feedback from Leadership Group. 

Early brainstorms at DSpace Release 9.0 Status.  Please feel free to add your own brainstorms or link in tickets that you wish to be considered. 

Goals for 8.1 / 7.6.3

Deadline is TBD for both 8.1 and 7.6.3.  Bug fix releases do not have fixed/scheduled deadlines. Instead, the developer team will determine when to create a release based on the significance of the issues to solve. (e.g. If major issues are fixed, then a bug fix release will occur more rapidly.  If minor issues are found, then a bug fix release may be delayed until sufficient fixes have been made to warrant a release)

  • Bug/security fixes only.  These minor releases will not include any new features.
    • New "themeable components" (for dspace-angular) are allowed in bug fix releases, provided that they don't significantly modify component behavior or similar.
    • Accessibility fixes are also allowed in bug fix releases, provided they don't significantly modify component behavior or similar.
  • Bug fix PRs should be created against "main" branch where possible. The "main" branch has the most strict code style rules. (i.e. PRs created against dspace-7_x  are becoming more difficult to port forward.)
  • Per our support policy, bug fixes are only guaranteed to be ported back to 8.x.  That said, where possible, we'll try to backport bug fixes (especially significant ones) to 7.6.x.
    • Keep in mind, if a specific bug fix is important to you in 7.6.x, then it is best to create two PRs (one for main and one for "dspace-7_x").  If you are able to provide a backport version of the PR, then we will merge it alongside the "main" branch version.
    • NOTE: In many scenarios, a backport to "dspace-8_x" should be possible to automate using the "port to [branch]" labels & the "Port merged Pull Request" GitHub Action

Try "Pull Request Trading" for a quicker review

Do you have a PR stuck in "under review" that you really want to see move forward?  Or maybe it's someone else's PR but you want to get it more attention?

See Trading reviews on Pull Requests for how to get immediate attention to that PR!

Notes

9.0 Release Updates

  • The 9.0 release is tentatively planned for April 2025
  • Updates will be shared as DSpace governance makes decisions as to the prioritization of 9.0 features

9.0 Release Status Board

  • Reminder: Steering gives general direction, not exact list of features; developers will therefore have some flexibility in terms of what is worked on / developed
  • While we wait for further direction from governance, the following high priority topics on the 9.0 Release Status Board can be worked on:
    • Improving performance / scalability 
    • Easier installation and upgrades
    • Code cleanup / maintenance

Ongoing Discussions

  • Developers/Committers are encouraged to continue to explore ways to improve code reviews and PR testing
  • Any ideas can be added directly to the Incentivizing Code Reviews and PR Testing wiki page or sent to Tim
    • Special interest can / should be given to 
      • Spin up code in virtual environment (quickly) for easier reviews/testing
      • Automated Code Reviewing resources
  • Discussed ongoing discussion tickets on GitHub
  • Archiving "dspace-api-lang" and move of Messages.properties translations to the backend
    • Will be moved to main repository / 9.0 status board

Upcoming Discussion

  • Enabling us of multiple database sessions per request (#8932): will work out how to move forward 
  • DOI topic: Pierre will take a look and start working on this

9.0 Project Board on GitHub

  • Lot of the tickets on the board are bug fixes and performance improvements, those can and will be backported to 8.1 and 7.6.3
  • Highlighted the "Needs Reviewers Assigned" column; discussed tickets on that column, gave updates, and assigned reviewers where possible
  • Any tickets that can be moved along quickly, let Tim know










  

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.