Page History
...
Issues / PRs for special attention (easy wins or "just one more +1!", and larger changes that need testers
| Issue | PR(s) | Category | Notes | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| PR#2693 (6.x) PR#2692 (master) | Big change | Adding 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) | ||||||||||
| PR#2710 PR#2704 (5.x port) | Big change | Adding ORCIDv2 authority control support to JSPUI This is a larger change that would benefit from more eyes and testers. | ||||||||||
| WIP (Kim) | 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) | ||||||||||
| 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. |
Issues merged for 6.4, waiting on something else (eg. porting to other another version, or documentation)
These issues are already fixed in 6.x branch but cannot be closed until they are forward-ported to master, or in the case of a security / critical bugfix, backported to 4.x and 5.x.
| Issue | Notes | Further work needed | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Already merged for 6.x but master Travis CI build has Unit Test errors which need fixing | port to master (5.x PR also exists) | ||||||||||
| Already merged for 6.x but master PR#2121 has conflicts - very simple conflict involving whitespace in the imports, by the looks... | port to master | ||||||||||
| Already merged for both fix versions but needs 6.x documentation (7.0 doc already added) just before 6.4 release | documentation (new feature) |
TODO
Do we need the full "first review, second review, test, merge, port" checklist here? Depends how our workload looks. Certainly if there are PRs people are lobbying for, a list might help. (see 6.3 equiv checklist DSpace Release 6.3 Status)
...
Overview
Content Tools