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, July 11, 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 Thursday, July 4 because of the USA Fourth of July holiday.  Tim Donohue will be out of the office from July 4-8, returning on Tuesday, July 9.

Agenda

  • Discussion Topics - If you have a topic you'd like to have added to the agenda, please just add it. 
    1. DSpace 7.6.2 release
      1. Congratulations to all on the 7.6.2 bug-fix release!
      2. Retrospective: Any thoughts to share on the process of this release?
    2. Managing Bug-Fixes to both 7.6.x and 8.x
      1. PRs should be created against "main" where possible.  It's the most strict about code style rules. (PRs created against dspace-7_x  are becoming more difficult to port forward.)
      2. Bug fixes are only guaranteed to be ported back to 8.x (per our support policy).  Where possible we'll backport bug fixes to 7.6.x. But, if that 7.6.x backport is important to you, then please create two PRs (one for main and one for 7.x)
    3. DSpace 9.0 release (tentative April 2025)
      1. 9.0 Board is created: https://github.com/orgs/DSpace/projects/31/
      2. Early ideas/brainstorms captured at DSpace Release 9.0 Status
    4. Ongoing Discussion: High CPU with DSpace 7 SSR: https://github.com/DSpace/dspace-angular/issues/3110
    5. Related to performance and SSR: Has anyone looked into SSG / prerender to let us create static pages/resources/app for delivery at least for some routes like DSO object pages? I just saw this and before I investigate more, wanted to raise it here and see if there are any hard blockers to us using it with dspace-angular: https://angular.dev/guide/prerendering     - Kim.
    6. (Other topics?)
  • Board Review & assignments:
  • Upcoming Topics: (Let us know if there are topics you want to discuss in future weeks)
    • None at this time

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.  Early brainstorms at DSpace Release 9.0 Status

Goals for 8.1 / 7.6.3

Deadline is TBD for both 8.1 and 7.6.3

  • Bug/security fixes only.  Release will occur when sufficient fixes have been made to warrant a release.
    • New "themeable components" (for dspace-angular) are allowed in bug fix releases, provided that they don't significantly modify component behavior or similar.
  • Bug fixes will need to be ported to "main", "dspace-8_x" and "dspace-7_x" 
    1. Ideally, it's best to start with a PR against "main" as that has the strictest code style rules. 
    2. 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
    3. Backporting to "dspace-7_x" may be trickier for some bug fixes (and require a manual port), as there are major code style changes between 7.x and 8.x

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

Release of DSpace 7.6.2

DSpace 7.6.2 was released on Tuesday, July 9, 2024. Tim Donohue thanked all committers for their work and their contributions towards version 7.6.2.


Discussed management of bug-fixes to both 7.6.x and 8.x

  • We are now maintaining three branches on GitHub (9.0, 8.x, 7.x)
  • Pull requests should be created against the main branch whenever possible
  • Per the support policy, bug-fixes are backported to the most recent major release only (in this case, version 8.0, see DSpace Software Support Policy); therefore bug-fixes will be backported to 7.6.x only if possible; for work on important bug-fixes that will be backported to 7.6.x, everyone is asked to create two pull requests: one for the 7.x branch and one for main
  • Tim will update the pull request template to ensure this rule is noted there. (DONE - for both DSpace and dspace-angular)


Discussed planning and ideas for work on version 9.0

  • Tim reminded the group that we are collecting ideas for the early discussion of what to prioritize for 9.0
  • Anyone is welcome to add ideas to the status board page on the wiki and to capture things we know we need to solve (DSpace Release 9.0 Status) 
  • Alternatively, ideas can be shared via direct messages to Tim Donohue or Holger Lenz, in the developer meetings, or as discussion items on GitHub 
  • Tim and Holger will be part of a smaller working group consisting of steering members to identify feature priorities for DSpace 9.0


Discussed the possible impact of SSR (Server Side Rendering) on performance





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