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.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Developers Meeting on Thurs, March 6, 2025

Time/Location

 from 15:00-16:00 UTC

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


Meeting time will remain at 15:00UTC until all countries have entered Daylight Saving Time

The USA/Canada start Daylight Saving Time (DST) on March 9.  However, Europe doesn't begin DST until March 30.  Until all countries have begun DST, our meeting time will remain at 15:00UTC.

This means for people in the USA/Canada, this meeting will occur one hour later for the rest of March. Our upcoming meeting schedule looks like this:

  • March 6 (today) at 15:00 UTC (10:00am EST)
  • March 13 at 15:00UTC (11:00am EDT - One hour later as USA/Canada will be in Daylight Saving Time)
  • March 20 at 15:00UTC (11:00am EDT)
  • March 27 at 15:00UTC (11:00am EDT)
  • April 3 at 14:00UTC (10:00am EDT).  As of April, all countries will be in DST, so the meeting will move back to its normal time of 10:00am ET.


9.0 Release Schedule

  • New Feature Development Deadlines
    • (tick) Feature PR Creation Deadline: Friday, February 21, 2025
    • Feature PR Review/Test Deadline: Friday, March 14
    • Feature PR Merge Deadline: Friday, March 28
  • 9.0 Release Candidate:  Friday, April 4
  • 9.0 Testathon: April 7-18 (two weeks)
  • 9.0 Translation updates: April 7-18 (during Testathon)
  • Bug Fix Deadlines
    • Bug Fix PR Creation Deadline: Friday, May 2
    • Bug Fix PR Merge Deadline: Friday, May 16
  • Documentation & Release Week: May 19-23 
  • 9.0 Release Announced: Monday, May 26, 2025

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. 

Priorities listed at DSpace Release 9.0 Status. 

Goals for 8.2 / 7.6.4

Deadline is TBD for both 8.2 and 7.6.4.  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

DSpace and DSpace-CRIS merger

  • Each planning group has had their first meeting, meeting notes are on the wiki
  • No updates at the moment, updates will be shared as things develop further

DSpace 9.0 release

  • #3506: Looking good overall, but some minor issues remain; Art shared update: should be finished by tomorrow
    • Angular 18 PR should also be done by tomorrow (#3717)
    • This has a massive number of commits (97), if anyone has time to clean it up, feel free to do so, otherwise Tim may have to do a squash merge
  • #4019: most of the changes are changing parts of the imports; if this is only the first step of moving to Nx, this might be difficult to do in 9.0; hard to say how much effort this may take
    • Recommendation: document more around how people are expected to be able to test this; if this is the last PR, this is the first thing that could get cut; if we want to get this into 9.0, reviewers need to better understand how to go about using it, what is the benefit of Nx, etc.
    • Do we have enough documentation on where what goes in the code, how it's been restructured and how people are supposed to work with the code? – Need to more documentation
    • Does this affect the potential merger? – No impact according to Giuseppe 
    • If this doesn't make it into 9.0, we can get it in right after 9.0 is released
    • Art, Tim have been assigned to review

9.0 Project Board

  • A number of things on the list came in last minute and need reviewers
  • #3740: Needs volunteer
  • #10129: Needs volunteer, Tim volunteered
  • #4016: Needs volunteer; Giuseppe, Tim volunteered to review
  • #10433: Open Alex integration; (front end: #4017); Pierre added as tester, Tim will review; this is of great interest to Steering, Tim will bring to Steering and ask if there are additional testers
  • #10434: Needs reviewers and/or testers; Pierre has been testing, has run into issue, will continue to test; Giuseppe will also review
  • #10435: Support for Matomo, similar to Google Analytics, just more GDPR compliant; front-end: #4018; Q: Do you need a Matomo account to test this? – Can be run by Docker, but also receive trial access through Matomo for testing; Art volunteered to test both front- and back-end; Tim also added
  • #10436: Giuseppe assigned
  • #4038: Translation files for #10434; small number of translation files for UI; Giuseppe added
  • #4022: Assigned to Tim; Other reviewers are welcome
  • #10451: New cover page implementation created by Pascal's team allows features for cover pages to no longer have to use the simple config strings, but rather uses an HTML template through Thymeleaf Library; Generally looks good, but would be better if we could use Velocity instead, so that we don't have to use another dependency
    • Options: either use as is using Thymeleaf and clean up later; or wait until after 9.0 and use Velocity; or use PDF template
    • Comment: seems that Thymeleaf is focused on HMTL while Velocity is much more general – it may be reasonable to have them both
    • Would love more feedback on which approach is best
  • Tim will working on more reviews today, others are encouraged to do the same so that we can get things merged rapidly

Other discussion

  • File Upload Max Limit: We have had a few institutions request increasing file upload limits, what is best practice? – Please ask on dev channel


Action items











  

  • No labels

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