Versions Compared

Old Version 1

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.

...

  • (30 mins) General Discussion Topics
    1. (5 mins) Any final things to get done for 7.0?
      1. Documentation tickets could use attention prior to 7.0 (or just after). At a minimum, we should try to link off to resources where they exist, so that early adopters of DSpace can find instructions/guides/workshops on various DSpace 7 features more easily.
    2. (15 mins) Atmire would like to claim https://github.com/DSpace/DSpace/issues/2834 (Enrich existing submission using search or identifier lookup)
      1. Strategy would be to revisit/update the "Metadata Suggestions" endpoint approach, to allow a way for submitters to see the metadata suggested by the search/identifier lookup & choose whether to accept the changes in the submission form.
      2. More details from Ben in the ticket: https://github.com/DSpace/DSpace/issues/2834#issuecomment-887580200
      3. Any quick feedback from the team on suggested approach?
    3. Early planning/assignments for 7.1. Claiming other tasks on 7.1 Board
      1. Tentative deadline for 7.1 would be end of October. (Similar to 7.0, may have an earlier internal deadline, e.g. Mon, Oct 18)
      2. Upcoming holiday/vacation schedules from team members? (Let Tim know if key team members will be out specific weeks)
    4. (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.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.
  • On Hold Topics
    • Discussing Release Numbering for 7.x
      1. Should we potentially have subminor (e.g. 7.0.1) releases to fix major bugs or security issues?  Or would those need to wait for the next minor (e.g. 7.1) release?
      2. Considering regular, scheduled releases instead of feature-based releases?
        1. Every two months quarter (3 months) release a new 7.x.  Features will be implemented in priority order, but not necessarily guaranteed for a specific release. 
    • Discussing Release Support after 7.0
      1. The DSpace Software Support Policy notes that we support the "most recent three (3) major releases" (where a major release is defined by the changing of the first number, e.g. 6.x → 7.x).  This would mean that 5.x, 6.x and 7.x are all supported once 7.0 is released.
      2. Should we propose to Committers / Governance a change of policy to the "most recent two (2) major releases"?  This would mean that we move to only supporting 6.x and 7.x.

...