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 ticket #779, REST PR #2129
Item Versioning (4Science) - REST PR #3371
~~Embargo entire Item, including metadata (4Science)~~ - UI ticket #767, REST ticket #2839
Collection harvested from an OAI-PMH endpoint and kick off a new harvest from the UI. (Atmire) - UI ticket #761
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 Contract #169
Numerous bug fixes & minor improvements (All team members)

...

(30 mins) General Discussion Topics
1. Review status of all features likely in 7.1 (see list above).
2. Demo site performance issues? https://demo7.dspace.org/ Is anyone else having slow load times & occasional "out of memory" crashes?
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.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.

...

Page tree