Table of Contents |
---|
Release schedule
- Friday, July 7 November 3 (Donated Feature Notification Deadline): Any community members who wish to donate a feature can contact VIVO tech team via some of the channels listed here - https://vivo.lyrasis.org/contact/, or open a GitHub issue at https://github.com/vivo-project/VIVO/issues. The VIVO 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.
- Friday, September 8 November 17 (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, September 22 December 29 (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, October 13 December 15 (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 October 27 December 29 (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 October 30 - November 3 January 8 - 12 (Documentation Week): Any merged PRs which don't have minimal documentation (how to enable / configure) MUST have documentation created this week.
- Week of November 6 - November 10 January 15 - 19 (Testing Week): any reported issue will be classified to release blocking or release non-blocking issue, all release blocking issue might be fixed before publishing release (if any)
- TuesdayThursday, November 14February 1: Public Release Announcement. VIVO 1.15.0 will be announced/released by this date.
Infrastructure
- GitHub Release branch
- will be created after releasing VIVO 1.14.0 - https://github.com/vivo-project/VIVO/tree/rel-1.15.0-RC
- new contributions are firstly merged into main branch, and before publishing release git cherry-pick is used to apply commits to rel-1.15.0-RC
...
- filters for searching
Jena 4one theme compatible with WCAG- responsive Wilma theme
- setting locale through a parameter
- role management upgrade (attribute based)
- I forgot my VIVO password
- Audit tool
REST API for CRUD operations over persons and organization units entitiesDecoupling VIVO deployment and building
...