Versions Compared

Old Version 13

changes.mady.by.user Jon Corson-Rikert

Saved on

compared with

New Version 14

changes.mady.by.user Jon Corson-Rikert

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 begin. Most releases include require several iterations of release candidates and testing to address problems detected in testing.

Selected JIRA issues:

Notes as of 12/16/14

  • recently made improvements to startup time after the first-time startup (saving approximately 20 seconds)
  • modularity improvements
    • reasoner (VIVO-778)
    • triple store (RDFService) (VIVO-225)
  • VIVO-909 and VIVO-907 – if change one of the ontology files, the entire reasoning has to be re-done – the TBox reasoning that takes 20 seconds triggers a full ABox re-inferencing
    • pointed out by Eliza in testing with Virtuoso
    • a maxCardinality property was being specified as a non-negative integer but was stored as an integer, so on startup the TBox reasoner interpreted an ontology change
      • saw the same thing in Virtuoso and TDB, but doesn't show the problem with SDB
        • got around it with a kluge to the Virtuoso driver – would like to distribute with that patch if can't get around it
      • worth a couple more hours to pursue – may be an issue in the general RDFService code, that is not used for SDB
    • steps to address this may also shave more time off the startup time
  • We will also need to distribute a patch for a SPARQL query syntax that Virtuoso doesn't accept

Finding and reviewing JIRA issues

VIVO application code

For the complete list of issues under consideration for VIVO v1.8, view the full, version-specific report in Jira.

...

VIVO-ISF ontology

Ontology issues for VIVO v1.8 have been managed in 3 places as the community workflow process evolves.

  1. Within the primary DuraSpace VIVO Project JIRA space
  2. In a older, now-deprecated DuraSpace VIVO Ontology JIRA space (a decision was made in 2014 to stop segregating ontology issues specific to VIVO from the main VIVO project JIRA space 
  3. In a tracker on GitHub, where VIVO-specific issues have been tagged with "question"

Documentation

Documentation issues for VIVO v1.8 are managed using the community/documentation component within the primary DuraSpace VIVO Project JIRA space.

...