...
Work in progress for the upcoming VIVO 1.8 release
Projected Release Timing
One outcome of the meeting of VIVO sponsors at the March, 2014 DuraSpace Summit even in Washington was a request to move to a regular release schedule where timing would be predictable and new features included only if ready. Any feature not on target to be finished by the code freeze data would have to be deferred until the next release.
...
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
View unresolved and recently-modified issues for the v1.8 release on the VIVO issue tracker.
Release Mechanics
The VIVO project uses the DuraSpace JIRA issue tracking system to manage issues and time tracking leading up to any given release. Issues are categorized as bug fixes, tasks, code tasks, or improvements, grouped into components such as ontology or testing or technical debt, and assigned a status based on criticality to the release.
The issue tracker is publicly viewable but to comment you need to sign up for a user account with DuraSpace. Accounts are shared between the DuraSpace wiki and issue tracker but the different DuraSpace projects including DSpace, Fedora, and VIVO each have different permission groups for access to project-specific wiki and JIRA spaces. Send us a note to be added to the VIVO wiki and JIRA spaces.
View unresolved and recently-modified issues for the v1.8 release. Note that issues are typically written as specifically as possible to provide clear requirements to developers and allow for realistic time tracking; when it makes sense, more detailed tasks are grouped as sub-tasks of a more general summary task.
When all issues marked with a status of blocker have been resolved, a code freeze is declared and a release candidate is prepared to allow Selenium (acceptance) testing to beginfor conducting acceptance testing, primarily with a set of Selenium tests. Most releases include require several iterations of release candidates and testing to address problems detected in testing.
...