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.
After today, for anyone in the USA/Canada, this meeting will occur one hour later for the next three weeks. 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 in USA/Canada, as they both will be in Daylight Saving Time)
March 20 - No Meeting(Tim will be on vacation most of this week)
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.
New Feature Development Deadlines
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
Discussion Topics - If you have a topic you'd like to have added to the agenda, please just add it.
(Time permitting) Migration to NX & refactor into libraries: https://github.com/DSpace/dspace-angular/pull/4019 (This may be delayed to immediately post-9.0 if we don't have time to give it a thorough test/review)
Other topics
Board Review:
9.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.
Discussion/proposal around refactoring and simplifying Live Import and External Data frameworks: https://github.com/DSpace/DSpace/issues/9758 (nothing concrete yet but would be great to get thoughts added to this issue and maybe find some collaborators)
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")
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 PRsshould 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?
This looks fine to move forward as is; there are still some minor things, but we can table those and talk about it later on
Once the dev gets back to it, Tim will be glad to re-review it
This replaces the existing cover page functionality; We should add a notice to the release notes that old cover page templates need a migration
Enhanced Login flow for ORCID Authorization feature #294
Need to get the merge conflicts resolved, otherwise hard to test
Tim has started doing code review, at least on backend
Art has volunteered to test
Will be in a good spot once merge conflicts have been resolved
ORCID Push Queue: add support for Products and Patents #9853
Adds new entity types for products and patents
Flagged as low priority – may want to delay these until the discussions around the merger is clearer; concern about entity types in 9.0 that don't have clear use cases, not requested from DSpace community
If anyone is interested in reviewing these, please let Tim know
Giuseppe: this is ported over from DSpace-CRIS
Does this PR affect the potential merger since DS CRIS use product and patent entities?
Yes, most likely; this should only be added if the merger seems clear
Happy to discuss this further
Integration of Google reCAPTCHA into DSpace Feedback Form #9866
Waiting on developer to solve merge conflicts
Others have permissions to rebase it, could move it forward, but may want to hear from the developer before touching their code
Code Refactor, marked high-priority, need to figure out how to move it in once the other things have been merged that are already on the list (Angular 18, control flow syntax)
Moved on to main list of big PRs
In meantime, Giuseppe and Tim will start to do code reviewing