Versions Compared

Old Version 1

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version Current

changes.mady.by.user Holger Lenz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To be decided by DSpace Steering Group with feedback from Leadership Group. 

Early brainstorms at Priorities listed 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.2 / 7.6.4

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)

...

See Trading reviews on Pull Requests for how to get immediate attention to that PR!

Notes

DSpace 8.1 / 7.6.3 releases

  • DSpace 8.1 and 7.6.3 have been released; congratulations and thank you to everyone who contributed; if any contributors are missing from the reference in the Release Notes, please let Tim know

DSpace 8.1 / 7.6.3 releases

...

...

DSpace 9.0 releaseRelease Schedule

  • Feature - PR creation date is coming up: February deadline is tomorrow, Feb 21, 2025
      This is a hard deadline; however, small extensions are possible if you
      • Anything that comes in after that will be tabled to 10.0
      • If anything is running late, let Tim know as soon as possible
      • Question: What about accessibility fixes? Does the PR-creation deadline apply to those? Answer: It depends on the accessibility fix: if it's a large, feature-like PR, it will fall under the Feb 21, 2025; however, most accessibility fixes tend to be smaller in nature and fall under the bug fix category (deadline of May 2)
      • Question: If anyone wanted to do translation work and don't miss any keys, would that be after the translation deadline? Answer: Most new translation keys are added during features; after the merge deadlines have passed and we are preparing for testation, that would be a good time to get any new translation keys in (early April, after March 28 Feature PR Merge Deadline)
        • Discussed how to improve the translation process workflow - Pierre Lasou will investigate and start the discussion with DCAT; Pierre mentioned the tool Weblate

    Other topics

    • Adding CSV export to DSpace Admin Reports
      • Pierre and Jeff Morin gave updates; PR is almost ready to go
      • Question: initial recommendation was scripts & processes type export; is it working this way? Answer: Yes
    • Adding more e2e (end-to-end) tests to the DSpace User Interface
      • Steering has discussed this and is eager to make this happen
      • Benefits: will make PR reviews easier; will also lessen the role of the Testathon and help out DCAT; also helps with dependency upgrades
      • This is not a hard lift - if anyone is interested in only doing 1 page, this could be done quickly; junior devs are encouraged to look at this; also an opportunity for Service Providers to give back code per the Registered Service Provider agreements
      • Question: can we split this in different subtasks? So that it can be done by more than one contributor. Answer: GitHub just added a new feature: creating sub-issues; can create subissues now if anyone wants to look at a particular aspect; Tim will start with creating a couple of subissues that he wants to look at; feel free to reach out to Tim or create your own subissue if you want to claim a specific feature on one page
    • Discussion of ticket https://github.com/DSpace/dspace-angular/issues/3070
      • Suggestion from Giuseppe is to remove the link from the thumbnail
      • Not a high priority item - we will continue to discuss this and think about it

    Board Review

    • Next deadlines after that is March 14 - initial review of Feature PRs - and March 28, Feature PR Merge Deadline

    Discussion Topics

    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)
      1. Upgrade to Bootstrap 5 (#3506)
        • Already assigned to Giuseppe and Tim
        • Moved to "Under Review" column
        • This upgrade impacts the themes
      2. Upgrade to Angular (#3717)
        • Assigned to Giuseppe
      3. 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
    • #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
    • There are still things in the "Under Review" column, please take care of those and final PRs created for features
    • Remove context parameter from AuthorityValueService methods (#9842)
      • Looks reasonable; but need to check if this could conflict with merger with DSpace-CRIS
      • Giuseppe assigned by Tim, he will review
      • Also need to look into whether we need the LogHelper.getHeader method (Line 223) - Mark H. Wood will investigate
      • Moved to "Under Review"
    • Provide new CoverPage implementation (#9844)
    • Looks like it's been moving along
    • Will bring to future discussion if necessary; there are some outstanding questions on the template engine (Thymeleaf)
      • If you have thoughts on this, add them to the comments in the PR


    Action items