Page History

...

Info

title	7.1 Release Plan

Tentative Release Schedule:

Thursday, September 23 (PR Create Date): every PR wanting to get into 7.1 should be created. Any created by this date are "guaranteed" in 7.1. Anything after may not be included in 7.1.
Sept 23 - Oct 14 (PR Final Reviews): code reviews & PR updates
Thursday, Oct 14 (PR Merge Date): every PR getting into 7.1 must be merged.
Monday, Oct 25: Internal/Early release goal. If possible, we'd like to release 7.1 in late Oct.
Monday, Nov 1: Public Release Deadline. 7.1 must be announced/released by this date.

Ongoing/Weekly tasks:

Tackle/Claim issues on 7.1 board (starting with "high priority")
Review/test all PRs assigned to you for review/testing: https://github.com/pulls/review-requested (Prioritize reviews of "high priority" PRs first)

7.1 likely new features (list not final)

Request a Copy, similar to how it worked in 6.x (Mark Wood & Atmire) - UI PR #1327, REST PR #2129
Item Versioning (4Science) - REST PR #3371, UI PR#1318
Collection harvested from an OAI-PMH endpoint and kick off a new harvest from the UI. (Atmire) - UI PR #1328, REST PR #7952
IIIF Support (Michael Spalti & 4Science) - UI PR #1079, REST PR #3210
OpenAIRE Funders as new External Source (Paulo Graça) - REST PR #3365
Import Entity Relationships via Simple Archive Format (tysonlt) - REST PR #3322
Bind/Configure Entity Type support for Collections & External Sources (4Science porting of DSpace-CRIS feature) - REST PR #7962
Numerous bug fixes & minor improvements (All team members)

...

(30 mins) General Discussion Topics
1. Finishing the 7.1 release. What is left to do before we cut the release?
  1. Any PRs still outstanding?
  2. Any new features that require documentation in https://wiki.lyrasis.org/display/DSDOC7x ?
    1. Request a Copy
    2. Item Level Versioning
    3. IIIF Support
  3. Finalizing the release schedule.
2. (Time permitting at end) Early look at a possible 7.2 Release Schedule
  1. Thursday, Dec 16 (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 6 (Code Review Deadline): All code reviewers should submit their feedback by this date. 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 13 (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. (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)
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.1 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.

...

On Friday, May 24th, This wiki will be down for a short time for scheduled maintenance between 6:00 and 8:00 pm Eastern time.

Page tree

Versions Compared

Old Version 1

New Version 2

Key