As of today (April 3) our Developer Meeting is now at 14:00-15:00UTC (10:00am-11:00am EDT), as all countries have entered Daylight Saving Time (DST). The meeting will remain at 14:00UTC until DST ends.
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?
Tomorrow is the 9.0 Release Candidate. This is not considered a stable release and should not be used in production. It's only to be used during the 9.0 Testathon for testing the new 9.0 features
Before Testathon: As much as possible, please document new features on our wiki . New features listed at 9.0 Release Notes. Most of these need to be linked up to documentation in the 9.0 docs.
If this cannot be completed before Testathon, then they can be worked on during testathon. However, undocumented features are unlikely to be as thoroughly tested.
9.0 Testathon starts next Monday (April 7) through April 18. Everyone is encouraged to participate.
It's important for developers to concentrate most on testing local installations and features/integrations that are not easy to test from the Sandbox Site (https;//sandbox.dspace.org)
DCAT members primarily test via the Sandbox site. Developers can help there as well if desired
9.0 Translations - During testathon is a good time to start translations of 9.0. As we have all features merged, it's less likely for new translation keys to be added to 9.0 in the coming weeks.
https://github.com/DSpace/dspace-angular/pull/4121 - Seems to have a lot of recent attention as it fixes search filters sometimes not loading on MyDSpace. Has several testers & this affects all branches. Alex & Tim assigned.
Next week's meeting: We'll check in about Testathon progress and see if anyone has found issues to discuss.
Feature PR Creation Deadline: Friday, February 21, 2025