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.

...

Warning

NO MEETING ON THURSDAY, NOV 25.  Because of the USA Thanksgiving holiday, we've cancelled that meeting. Our next meeting will be on Thursday, Dec 2.


Info
title7.2 Release Plan

Tentative Release Schedule:

  • Thursday, Dec 23 (PR Creation Deadline): All new feature (or larger) PRs should be created by this date. (Smaller bug fixes are welcome anytime)
  • Thursday, Jan 20 (Review/Test Deadline): All code reviewers or testers should submit their feedback by this date. Code reviews must be constructive in nature, with resolution suggestions. Any code reviews submitted AFTER this date will be considered non-blocking reviews. This means feedback received after Jan 20 is optional to address (unless the team or PR developer decides it is required).
  • Thursday, Jan 28 (PR Merge Deadline): All new feature PRs should be merged by this date. (Bug fixes can still get in, as long as they are small or important)
  • Monday, Jan 31: Internal / Early release goal. If possible, we'd like to release 7.2 in late January or first week of Feb.
  • Monday, Feb 7: Public Release Deadline. 7.2 must be announced/released by this date.

Ongoing/Weekly tasks:

...

  • (30 mins) General Discussion Topics
    1. Planning 7.2 Release Features
      1. Finalizing the work assigned to Atmire & 4Science: Any outstanding questions remain? 
      2. (Discussion) Migrate extra DSpace-CRIS “Live Import” (Scopus, Web of Science, CrossRef & OpenAIRE) sources to DSpace core: https://github.com/DSpace/DSpace/issues/3359
        1. Updated estimate from 4Science: 48 hours.
    2. Are there features which we know will need additional review/tester help?
      1. Testing DSpace 7 Pull Requests - Step by step instructions to help anyone (even non-technical folks) test a PR using Docker & GitHub CLI
    3. (Other Topics?)
  • (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.2 Project Board - Assign tickets to developers & assign PRs to reviewers.
      • Paid (by DSpace project) developers must keep in mind priority. If new "high" or "medium" priority tickets come in, developers should move effort off of "low" priority tasks.
      • Volunteer developers are allowed to work on tickets regardless of priority, but ideally will review code in priority order.

...