...
- Back-porting bug policy, redux
- Blank nodes plan
- Migration tooling plans
- New JIRA tickets
Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1363
- Audit Service design
- Islandora
- ...
Minutes
- Back-porting bugs
- Other projects:
- dspace security patches go back 3 releases, bug patches are a best effort, sometimes going back one release
- ubuntu has long-term support releases that are supported for 5 years
- What is our goal for a policy
- Michael Durbin brought up that backwards compatibility should be considered
- Andrew Woods indicated that our release policies (minor releases are non-backwards compatible, point releases are backwards compatible)
- Michael Durbin suggested not backporting to point releases ever
- Unknown User (acoburn) thought that for minor releases there was no need to backport
- Unknown User (escowles@ucsd.edu) brought up the point that as the installed base grows, there may be prevalence of adopters who are more hesitant to keep up with the latest version.
- Andrew Woods observed that perhaps we should wait to establish a policy at this time
- Unknown User (escowles@ucsd.edu) said that we're in "early adopter mode" and don't support backporting, but later we may move to a more stable mode where we support the last 2 minor versions.
- there appeared to be a consensus around this, and making a statement to the community about this including a definition about major, minor and point releases.
- someone will make this statement to the community
- Other projects:
- Blank Nodes
Minutes