The USA/Canada began 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.
For anyone in the USA/Canada, this meeting will occur one hour later until end of March. Our upcoming meeting schedule looks like this:
March 20 - No Meeting(Tim will be on vacation most of this week)
March 27 at 15:00UTC (11:00am EDT - Still one hour later in USA/Canada)
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
(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
(Please add any here that you'd like to discuss)
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.
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?
Reminder that next week this meeting will shift to 14:00UTC (10:00am ET). For Europeans, this means it will be the same local time as this week. For North Americans, this moves the meeting (back) to one hour earlier (i.e. the same time it was before daylight saving time began). We'll stay at 14UTC until daylight saving time ends in the Fall.
DSpace & DSpace-CRIS Potential Merger - Nothing to discuss. These groups are not far enough along to ask for community feedback or share any early discussions/ideas. We're still in the early learning phases of the discussion.
DSpace 9.0 Release Schedule dates
TOMORROW (Friday) is our merger deadline for Feature PRs. We have a small amount of flexibility in that it may be possible for a few Feature PRs to be merged early next week (if they are showing good progress by the end of this week). Any Feature PRs not showing progress by end of this week will be rescheduled for 10.0
Once all feature PRs are merged, please help to test the system for any major bugs. This could be simply testing the Sandbox site: https://sandbox.dspace.org , or testing on your own local machine with the latest "main" branch. (Tim will ping developers on Slack next week, hopefully by Weds, when testing would be helpful)
Overall, positive feedback from Tim. Just an outstanding accessibility issue.
Giuseppe notes that he has some concerns about this PR. He's worried it's "overengineering" and may be problematic. He will write his concerns down in a review later today
Noted that code reviews were due by the code review deadline (March 14). So, we need to keep that in mind for any late reviews. Tim agrees, but wants to understand the concerns better. Maybe there's a way to solve some of them quickly?
Tim also notes this might be considered a "nice to have" from a production perspective. It's a very useful PR for developers, as it makes it easier to customize menus & less likely to encounter merge conflicts when doing so. But, it doesn't add any real "new features" for production (unless you are modifying these menus in your site)
We need to decide quickly what to do about this PR (by early next week at the latest).
Unfortunately no one has had time to review this (too many other open PRs). This will need to be delayed until the 10.0 release. However, if we can start to look at it during the 9.0 release process, then hopefully we could consider merger immediately after the 9.0 release.
We'll do our best to get others in, especially if they are having positive feedback. But, a larger number of Feature PRs are "stalled" and waiting on the developer to respond – these are all likely to be dropped from the 9.0 release unless they are updated today or tomorrow.
Feature PR Creation Deadline: Friday, February 21, 2025