Versions Compared

Old Version 5

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 6

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. Finishing the 7.1 release. What is left to do?
      1. New features that require documentation in https://wiki.lyrasis.org/display/DSDOC7x: 
        1. Request a Copy (Mark Wood)
        2. Item Level Versioning (4Science)
        3. OAI Harvester (Atmire)
        4. (tick) IIIF Support (Michael Spalti)
        5. (tick) Collection & External Source configuration for Entity Type (Tim)
        6. (tick) Upgrade & Release Notes (Tim)
      2. Finalizing the release schedule.  Cut the release Thurs (28th). Announce Nov 1.
    2. Finalizing 7.2 Release Schedule (DATES UPDATED)
      1. Thursday, Dec 23 (PR Creation Deadline): All new feature (or larger) PRs should be created by this date. (Smaller bug fixes are welcome anytime)
      2. (NEW) Thursday, Jan 13 (Code 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 6 is optional to address (unless the team or PR developer decides it is required).
      3. Thursday, Jan 20 (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)
      4. Monday, Jan 24: Internal / Early release goal. If possible, we'd like to release 7.2 in late January.
      5. Tuesday, Feb 1: Public Release Deadline. 7.2 must be announced/released by this date.
    3. 7.2 Development Processes
      1. Recommended to claim a task on the 7.2 board: https://github.com/orgs/DSpace/projects/14  (Currently this contains only "Tier 1 - Highest Priority" features & known bugs)
      2. You may also claim tasks on other boards (or not on a board), but only if that work will be "donated" to DSpace.  (I.e. paid work must be from the 7.2 board, while volunteer work can be anything)
    4. (Time permitting at end) Early thoughts on REST API performance issues documented at https://github.com/DSpace/DSpace/issues/7971 (this work will be for 7.2 or later)
    5. (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.

...