Page History

...

• Discussion Topics - If you have a topic you'd like to have added to the agenda, please just add it. 
  
  1. Open Repositories 2025
     
     1. OR2025 DSpace Developer Meet-Up and Q&A (Workshop) - Sign up if you'd like to share your work or suggest a topic for discussion!
     2. DSpace at OR2025 - Wiki page of known DSpace-related talks to be presented at OR2025
  2. DSpace & DSpace-CRIS potential merger discussions
     1. DSpace and DSpace-CRIS Planning Groups - wiki pages to follow along with ongoing discussions.
     2. DSpace-CRIS and DSpace Differences  - List of known feature/architectural differences between DSpace 8 and latest version of DSpace-CRIS
  3. DSpace 8.2 and 7.6.4 maintenance releases
     1. Maintenance Board (9.x, 8.x, 7.6.x)
     2. Backporting recent bug fixes.
        1. Frontend fixes flagged with "port to dspace-7_x" and "port to dspace-8_x"
        2. Backend fixes flagged with "port to dspace-7_x" and "port to dspace-8_x"
     3. Release just after Open Repositories?  Tentative Date: Thursday, June 26?
  4. DSpace 10.0 (Very Early Days)
     1. 10.0 Board: https://github.com/orgs/DSpace/projects/32
     2. 10.0 Priorities: DSpace Release 10.0 Status (Depends heavily on a final decision around potential merger with DSpace-CRIS)
  5. Other topics
     
     (Please add any here that you'd like to discuss)
     1. Sascha's work on Solr queries (multiple PRs) and suggestion to switch to the eDisMax query parser
• Board Review:
  • 10.0 Project Board - Review PRs collaboratively or Assign new PRs to volunteers to code review and/or test.
  • Backlog Board - Are there any tickets here stuck in the "Triage" column?  We'd like to keep this column as small as possible.
  • Maintenance Board (9.x, 8.x, 7.6.x) - Known bugs can be found here, along with any backported bug fixes.
• Upcoming Topics: (Let us know if there are topics you want to discuss in future weeks)
  
  • Ongoing Discussions (temporarily put on hold until there are updates):
    1. High CPU with DSpace 7 SSR: https://github.com/DSpace/dspace-angular/issues/3110  (This should be alleviated through several SSR related performance improvements in 7.6.3 and 8.1)
    2. Simplifying the Installation Process: https://github.com/DSpace/dspace-angular/issues/3184
  • Discussion: how to keep message catalogues in sync? https://github.com/DSpace/dspace-angular/issues/3334

...

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

Notes

10.0 Release Schedule

• A tentative release schedule for 10.0 is out - see top of this page

Open Repositories 2025

• Developers Workshop: If you are attending, please add topics that you would like to discuss to OR2025 DSpace Developer Meet-Up and Q&A
• Other DSpace-related presentations at OR25 can be found at DSpace at OR2025
  • This page will include slides after OR25 is over
• There will be no developer meeting on June 19

Merger Discussion

• No major updates; for meeting notes, see DSpace and DSpace-CRIS Planning Groups
• There is another technical group meeting today
• Updates will be shared as new developments occur

Maintenance Releases

• We have some backports that are still left to do
  • Frontend fixes flagged with "port to dspace-7_x" and "port to dspace-8_x"
  • Backend fixes flagged with "port to dspace-7_x" and "port to dspace-8_x"
• Release date is planned for late June or early July (tentative date: June 26)

DSpace 10.0 Release

• If anyone sees anything on 10.0 Release Board that's a bug fix and you'd like to get it moved forward, please bring it up to see if we can get a volunteer to review it (or use Slack to ping the dev channel to see if you can find a reviewer)
• See DSpace Release 10.0 Status; 10.0 is not yet formally finalized; priorities will depend on outcome of potential merger discussion
• Discussed https://github.com/DSpace/dspace-angular/issues/3807
  • Tim will create a follow-up ticket to summarize the discussion and brainstorm ways we want to improve this more in the future
• Discussed https://github.com/DSpace/dspace/issues/10236
  • A default lang value can cause problems with metadata cleanup later on
  • If we do keep it, we may need to provide a warning that there may be incorrect marking
  • Tim will summarize the discussion in the ticket

Action items