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, January 30, 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


9.0 Release Schedule

  • 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

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. 

Early brainstorms at DSpace Release 9.0 Status.  Please feel free to add your own brainstorms or link in tickets that you wish to be considered. 

Goals for 8.1 / 7.6.3

Deadline is TBD for both 8.1 and 7.6.3.  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

  • Reminders about 9.0 deadlines coming up (see note at the top of the agenda)
    • Will be strict about the Feature PR deadline.  Any major features or changes not in PR form by Feb 21 will not be considered for 9.0 (unless you notify Tim in advance of Feb 21 and we work something out)
  • Discussion of Giving someone Workflow privileges (Reviewer, Editor, Final Editor) also gives them submit privileges:  https://github.com/DSpace/dspace-angular/issues/3849
    • Several Committers not surprised by this behavior.  We are only checking for "ADD" privileges to determine if you can ADD content to a Collection (i.e. submit).  Workflow privileges also  require ADD privileges in order to allow them to edit in-progress submissions (for Editor & Final Editor roles). 
    • This doesn't seem high priority for 8.1 at least.  Needs more discussion to determine if there's a way to separate these permissions better
    • Several note they are not concerned about this.  Not seen as a major issue as those who are doing workflow approval are "trusted". They do not gain submit to other collections. They only can submit items back into the same workflow approval process.
    • Tim will update the ticket with this feedback
  • Most of the meeting was spent on 8.1/7.6.3
  • Goal for 8.1/7.6.3 is still January 30.  However, because of the large number of PRs still open, this may be a difficult deadline .  It may be more likely that the release will occur by February 6. 
    • That said, we are doing our best to get this out on/by Jan 30. If we miss that deadline, it will be out by Feb 6 (assuming no other complications, obviously)


Action items











  

  • No labels

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