Page History

...

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
  • search indexing (VIVO-869 being the parent issue)
  • 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

VIVO application code

...