Page History

...

1. 1. Code freeze

   2. Create a new release candidate

   3. We will be testing vivo-ontology-lab pull request. https://github.com/vivo-project/VIVO/pull/63

   4. Is it good to go in production?

   5. Preparing documentation for release (LEAD - Mike)
      1. Create release "change log"
      2. Create release "upgrade notes"
      3. Does ingest documentation need to be revisited?
   6. Evaluation of Jena2 and Jena3 tools 
   7. Work through and document upgrade from 1.7

   8. Team: Mike Conlon (VIVO) Muhammad Javed (Cornell) Benjamin Gross LEAD (Clarivate) Ralph O'Flinn (UAB), Jim Blake (Cornell), Don Elsborg ( CU Boulder )

   9. DELIVERABLES:

   1. Pull request merge in dev (and merge to master??)

   2. Updated documentation following evaluation of current state of 1.10 documentation. Don Elsborg volunteered to assist as 1.7 persona. 

      1. Upgrade a CU Boulder 1.7 dev instance with local customizations to 1.9 — updating documentation as appropriate

      2. Upgrade CU Boulder 1.9 dev instance to 1.10 with local customizations 

      3. Verify single vivo.owl file and address local customizations for CU Boulder instance. 

...