Versions Compared

Old Version 2

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version Current

changes.mady.by.user Tim Donohue

Saved on

Key

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

...

Info
title7.0 Final : Next Steps / How to get there
  1. Final analysis of Testathon feedback
    1. VOLUNTEER HELP APPRECIATED: (Maureen & Bram at DCAT have been asked to help with this) Final review of Test Plan spreadsheet. Ensure all feedback/bug reports are captured in GitHub Issue tickets (most already should be), so that we can prioritize, etc
    2. UNTESTED TASKS (needing volunteers)::
      1. (Andrea Bollini (4Science) and Tim Donohue will work on getting this setup on https://api7.dspace.org/server/ so that it can be tested on our demo site)
      2. Test Handle Server setup/functionality with a real handle prefix (see T044 in Test Plan spreadsheet).  Make sure hdl.handle.net URLs are redirected properly (as this was overlooked during Testathon)
      3. (Needs volunteer) DSpace 7 Security Analysis (In our dev process, we have been running automated security checks, but an external analysis would be nice)
      4. (Needs volunteer) DSpace 7 Performance Analysis (In our dev process, we've done past performance analysis, but more "real life" checks would be nice)
  2. Final analysis of Accessibility Results (from Deque) - assigned to Tim Donohue 
    1. Analyze all "Critical" (72) and "Serious" (293) accessibility issues (link requires login). Turn into GitHub Issue tickets & prioritize & assign for estimation
  3. Estimating/Announcing 7.0 Release Date
    1. Requires estimating all high/medium priority TBD tickets: https://github.com/orgs/DSpace/projects/5?card_filter_query=label%3A%22estimate+tbd%22
    2. Requires completing both analyses above
  4. Ongoing bug fixing / code reviews of remaining 7.0 tickets (with concentration on high/medium priority)
    1. Fix all "high priority" bugs and ideally all "medium priority" bugs on our 7.0 board
    2. Review/test all PRs assigned to you for review/testing: https://github.com/pulls/review-requested
  5. Finishing 7.0 Technical Documentation
    1. More eyes on Installing DSpace (especially the Angular UI instructions)
    2. See also, Documentation tickets at https://github.com/orgs/DSpace/projects/5?card_filter_query=label%3Adocumentation

...

  • (30 mins) General Discussion Topics
    1. Reminder: Open Repositories starts in just over 3 weeks (Monday, June 7)
    2. Majority of tickets left on our 7.0 board are for User Interface estimation/work.  The availability of UI developers will have a great impact on how quickly we can release 7.0
      1. UI tickets: 56 total (49 in estimation/unclaimed, 7 in progress) (more likely to be created as analysis of Accessibility tests and testathon finishes)
      2. REST tickets: 10 total (8 in estimation/unclaimed, 2 in progress)
      3. Documentation tickets: 8 total
    3. (Tim to bring brought to DCAT) Item Mapping Permissions question: https://github.com/DSpace/DSpace/issues/3261
      1. Should Collection Admins be allowed to map any Item into their Collection? (6.x behavior)  Or just Items which they have WRITE privileges on? (current 7.x behavior)
      2. FEEDBACK FROM DCAT: Those who responded all said the current 7.x behavior seems fine to them.  Collection Admins should likely not have this control unless they administer multiple collections.
  • (30 mins) Planning for next week
    • Review the Backlog Board - Are there any tickets here stuck in the "Triage" column?  We'd like to keep this column as small as possible.
    • Review the 7.0 Project Board - Assign tickets to developers & assign PRs to reviewers.
      • Priority should be kept in mind here. If new "high" or "medium" priority tickets come in, developers should move effort off of "low" priority tasks.  Reviewers/testers should also concentrate effort on "high" or "medium" priority PRs.

...