Versions Compared

Old Version 12

changes.mady.by.user Hrafn Malmquist

Saved on

compared with

New Version 13

changes.mady.by.user Kim Shepherd

Saved on

Key

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

...

Tentative cut-off for PR merging:

April 14 May 1 2020

Suggested pre-release application (usability, functional) tests for DSpace 6.4

...

Issues / PRs for special attention (easy wins or "just one more +1!"), and larger changes that need testers

IssuePR(s)CategoryNotes

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyDS-4440

PR#2693 (6.x)

PR#2692 (master)

Big
Bigger changeAdding an 'Anonymize Statistics' feature to DSpace for GDPR compliance. Most of the discussion is on JIRA and on the master PR #2692. Consensus so far is that it works well, is definitely worth trying to get into 6.4, but could do with a bit more testing just to ensure no data loss to stats docs can occur in various conditions (see last master comment)

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyDS-2715

PR#2710

PR#2704 (5.x port)

Big
Bigger changeAdding ORCIDv2 authority control support to JSPUI
This is a larger change that would benefit from more eyes and testers.

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyDS-3940

WIP (Kim)
https://github.com/DSpace/DSpace/pull/2739Bigger
Big
change

Support for SHERPA ROMeO API ends on April 14. Kim Shepherd is working on a PR to work with the new JSON APIv2. The data structure is quite different and the use of colours is not encouraged so much anymore, so there are a few questions around what to change, what to try and fit back into the old view/model, etc. (see JIRA convo)
This would be really good to get into 6.4 as all SHERPA lookups will start breaking after mid-April.

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyDS-3945

PR#2191
PR#2113
PR#1730 (merged)
PR#2464		Competing PRs

A small bugfix, but there seem to be three PRs with similar solutions.
I think we prefer PR#2113 as it is a bit more robust, but...
I think PR#1730 might already fix the issue - needs testing. And PR#2464 is trying to fix a starts by issue and has a conflict with the changes merged from #1730.

In short: I think  this issue might either be fixed already in 6.x, or just needs PR#2113 to merge. Would appreciate a second opinion.

I could not replicate the issue described in PR#2464 when using a build off 6_x. I tried browsing authors, titles and subjects, with RPP = 2 to compensate for the relatively little content on my test database.
I think we should merge PR#2113 and skip these other two. Having said that, I do not feel like I can be 100% about this. -- Hrafn Malmquist


Issues merged for 6.4, waiting on something else (eg. porting to other another version, or documentation)

...