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. (tick) Final analysis of Testathon feedback
    1. VOLUNTEER HELP APPRECIATED: (Maureen & Bram at DCAT have been asked to help with this) (tick)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:
      1. (tick) (DSquare Technologies is helping with thisran an initial scan, see summary on wiki page) DSpace 7 Security Analysis (In our dev process, we have been running automated security checks, but an external analysis would be nice)
      2. (warning) (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. (tick) (COMPLETED) 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. Any final OR2021 prep/questions from anyone?
    2. Setting a release date for 7.0
      1. Assuming only "high priority" tasks (~80hrs of estimated dev work).  "Medium priority" tasks become "nice to have", but many/most will be delayed to 7.1
      2. Tentative Dates for 7.0 Final release :schedule.
        1. June 24: every 7.0 PR created (concentration on "high priority"). Any created by this date are "guaranteed" in 7.0. Anything after may not be included in 7.0.
        2. Monday, Aug 2: Public Release Date
          1. Internal Release Goal: Monday, July 26 (i.e. we will release early if possible to do so)
        3. July 15 every PR merged
        4. June 24 - July 15 code reviews & PR updates (Art out week of July 12, Ben out week of July 5, Tim out week of July 5, Andrea out June 23-July 2)June 24 every PR created (high priority mainly) - Guaranteed in 7.0, anything after may not be in 7.0
        5. July 15: every 7.0 PR merged
        6. Monday, Aug 2: Public Release Deadline
          1. Internal Release Goal: Monday, July 26 (i.e. we will release early if possible to do so)
    3. Ranking of outstanding 7.x features (by DSpace Governance): DSpace Release 7.0 Status#7.x
  • (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.

...