Page History
...
See Trading reviews on Pull Requests for how to get immediate attention to that PR!
Notes
9.0 Release Schedule
- Feature PR deadline is tomorrow, Feb 21, 2025
- Anything that comes in after that will be tabled to 10.0
- If anything is running late, let Tim know as soon as possible
- Next deadlines after that is March 14 - initial review of Feature PRs - and March 28, Feature PR Merge Deadline
Discussion Topics
- First Meeting of the DSpace & DSpace-CRIS Technology Planning Group happened last week Thursday
- This meeting was mainly to get everyone up to speed, no other news or reports at this point
Board Review
- Needs Reviewer Assigned column: Tim flagged a few PRs as high priority (mostly code relating to upgrades) to try to make sure they go into 9.0
- Many of these PRs have merge conflicts, please work on these to resolve the conflicts so that we can make these easier to test
- Want to go through the following three PRs in order (as each impacts the other)
- Upgrade to Bootstrap 5 (#3506)
- Already assigned to Giuseppe and Tim
- Moved to "Under Review" column
- This upgrade impacts the themes
- Upgrade to Angular (#3717)
- Assigned to Giuseppe
- Migration to Angular Control Syntax (#3997)
- Would like to get testers for these
- Tim assigned to this one in addition to Art
- This one shouldn't impact the themes
- Giuseppe: they will resolve the merge conflict once the other two have been merged
- Upgrade to Bootstrap 5 (#3506)
- #10432: Gets us off the old date classes on the backend in Java, which should resolve the time zone problems that we occasionally see in DSpace
- Does not work and is not testable yet; Tim will try to work on this tomorrow so that it's testable
- Mark has volunteered and been assigned
- Kim Shepherd has volunteered to test dates and been assigned
- Nick can also test whenever it's ready, has been assigned
- #3994: Affects the way the menus are structured in the Angular UI
- Not as high priority, but want to keep it in mind
- Would come after the Bootstrap Angular Control Flow, in a week or two
- Giuseppe volunteered and was assigned; Tim also assigned himself
- Other non high priority PRs:
- #9844: Why was Thymeleaf chosen? Pascal will answer the question in the discussion section
- Need to continue the discussion on this, Tim added to this one
- #3349, #3355, #9849: all related PRs around ORCID Login
- Tim added, Art added
- #3357: Does this add default entities for products and patents? Yes, it seems like it does
- Do we have any concerns about adding products and patents to DSpace? Do we see this as a good fit for the DSpace data model?
- Several of these ORCID-related PRs come out of the ORCID community, funded by ORCID
- Need reviewers or testers for this - There are already some testers who are looking at this
- Tim assigned to himself
- If anyone is interested, please test this
- #9848: skipped for now
- #9866:
- Need to get the merge conflict resolved on these PRs from the developer
- Yury, Kim was assigned
- #10407 and #3984: Yury, Martin added
- #9912, #3507: potentially conflicts with DSpace-CRIS, skipped for now
- #3338: needs to have merge conflict resolved by developer, assigned to Alex; Tim will review backend PR (#9882)
- #3540: allows to put geospatial data in metadata to be rendered in a map on search results or item page
- treated as stand-alone, not dependent on other PR
- need merge conflicts resolved and testers
- backend is small, front-end a bit larger
- Giuseppe, Tim will review; Eike volunteered as tester (GitHub handle: Leano1998)
- #3722: needs testers and review; related to edit metadata fields
- Giuseppe volunteered as reviewer
- #3740: Adding a contact telephone field to the UI
- Not high priority, will table this one for the moment
- #10129: make text extraction into XML document from PDF possible
- Also not high priority; related issue is #10105
- If anyone is interested, reviewers and testers are welcome
- Mark: ask contributor for explanation on how this is intended to be used
- #10170: Tim assigned himself
- #3785: Probably not high priority, but this is very small
- Giuseppe volunteered as reviewer
- #10237: try to find a way to allow the submission form to autocomplete values based on existing metadata values
- If anyone interested, additional testers or reviewers are welcome (Damian already assigned)
- Is using the SOLR suggestion authority?
- Giuseppe volunteered to review
- #10294, #300, #3882: Yury and Tim added
- #10333: No volunteers at the moment, not high priority
- Tim added himself
- #3987 and #10410: Tim added himself; need additional testers and reviewers
- #10431 and #4016: allowing ability to have labels for alternative content
- #9844: Why was Thymeleaf chosen? Pascal will answer the question in the discussion section
- There are still things in the "Under Review" column, please take care of those and final PRs created for features
Action items
Overview
Content Tools