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?
Technical Planning group is still doing a detailed review of DSpace-CRIS and DSpace Differences. Should be done in our next meeting, and we'll start to focus on which feature require more discussion or bring up concerns regarding the potential merger.
DSpace 8.2 and 7.6.4 maintenance releases
Please backport any PRs to 7.x or 8.x which are flagged with at "port to" label. We'd like to get these into the maintenance releases
Tentative release date is after Open Repositories. Maybe on Thursday, June 26?
Question: Do we have any idea when 8.3 would come out after 8.2 is complete?
We don't schedule maintenance releases. They come out as necessary. It's difficult to say when 8.3 will be released, as it may depend on when major bugs are needing to be fixed.
That said, Committers can help to make a release happen earlier if they are willing to take the lead on the release.
Every release requires a leader/steward for that release. Tim often is that steward, but this can mean that maintenance releases are less frequent simply because he attention is split. If another Committer wants to do a maintenance release, then it can come out earlier
DSpace 10.0
General priorities now listed at DSpace Release 10.0 Status. These may change once a decision is made on DSpace-CRIS potential merger.
Open Discussion
https://github.com/DSpace/dspace-angular/issues/1834 - Collection/Community browse options are always the same, even for Entities. This ticket is becoming annoying for sites that use Entities, as the browse options don't make sense for some entities (like Person)
Giuseppe notes this issue is fixed in DSpace-CRIS. It lets you change the browse options (in Discovery) based on the Collection or the Entity Type. So, if the DSpace-CRIS merger goes forward, this ticket will be "fixed". If it doesn't go forward, we'd likely want to port this from DSpace-CRIS
Pierre will talk in a future meeting about how this PR is used at his institution & re-introduce this discussion to everyone. That way we can make a decision on it on how to move it forward.
General reminder: If something you worked on or cared about has been lost or forgotten, please do draw our attention to it. We have a massive community and good ideas sometimes get lost or temporarily set aside. If you bring them back up during a time where things are less rushed, we'd be glad to revisit them.