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.

...

Info
title7.5 Release Plan

Release Schedule:

  • (tick) Thursday, December 1 (Donated Feature Notification Deadline): Any community members who wish to donate a feature to this release must notify Tim Donohue by this date (either via email, Slack or GitHub). The DSpace 7 team will then provide feedback on whether it will be possible to include this feature in the release (based on team member availability and the size of the feature).  Early notifications are more likely to get included in the release.
  • (tick) Friday, December 23 (Feature PR Creation Deadline):PRs should be created by this date if they are to be reviewed in time for the release.  Please note there is no guarantee that a PR will be included if it is created by this date. Larger PRs are recommended to be created earlier, as that makes it more likely they can be reviewed in time for inclusion. (Smaller bug fixes are welcome anytime)
  • Friday, January 27 (Feature PR 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. NOTE: Larger PRs or donated PRs may have their own deadlines established for PR creation, review and merger.This deadline only applies for PRs with no other deadline established.
  • Friday, February 3 (Bug PR Creation Deadline): Bug fix PRs are still acceptable after this date if they are very high priority.  However, any submitted after this date will likely need to have pre-assigned reviewers in order to ensure the review can be completed before the PR Merge Deadline.
  • Friday, February 10 (PR Merge Deadline): All PRs should be merged by this date.  (Note: bug fixes can still get in after this deadline, as long as they are small or important)
  • Week of February 13 (Documentation & Release Week):  Any merged PRs which don't have minimal documentation (how to enable / configure) MUST have documentation created this week. Later in this week (around Thurs) will be the 7.4 5 release.
  • Monday, February 20: Public Release Announcement. 7.4 5 will be announced/released by this date.

Ongoing/Weekly tasks:

...

  • (30 mins) General Discussion Topics
    1. Any new updates / brainstorms about improving initial response speed of DSpace 7 UI ?  See DSpace 7 UI Optimization Analysis and https://github.com/DSpace/dspace-angular/issues/1921
      1. NOTE: In a new ticket (https://github.com/DSpace/dspace-angular/issues/1954) related to this issue, it was mentioned that DSpace 7.2 has much better homepage performance than DSpace 7.4.  We may want to look closer at what major changes occurred between these releases that could have impacted performance.
      2. NEW: Caching of SSR pages: https://github.com/DSpace/dspace-angular/pull/2033
    2. Any updates on Demo Site issues (https://demo7.dspace.org/ and https://api7.dspace.org/server/)?  
      1. LYRASIS is still working on migrating demo site to our infrastructure (and using Docker). Likely not to be completed until Jan/Feb 2023 at the earliest
      2. In meeting on Dec 15, we narrowed down issues as likely being on the backend.  Backend is throwing occasional 500 exceptions (possibly rate limiting?).  4Science team was going to look closer at logs to see if we can figure out why this is occurring.
    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.5 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

...