Page History

Completed Sprint - Sprint 212 (Sept 4 - Sept 29)  – Burndown Report

Current Sprint  - Sprint 213 (Oct 2 - Oct 27) LINK TO Jira Sprint 213

For the month of October 2023, the Mayo group is planning to:

• Complete Report Exporter refactoring and dependency updates

  • (see EVSREPEXP-475 -> 483)

• RMI Retirement - in progress

  • Unfortunately, I do not have a detailed update at this time, other than there are efforts to update the test script. I believe that the the RMI is turned off on STAGE, and the test script would test other components to verity that there are no unseen side-effects.

• Improvements, Refactoring Code Debt, Feature development:
  • LEXEVS-5341 Update Spring to Spring 6
  • LEXEVSCTS2-453 Update CTS2 welcome with digital sytle requirements (header, footer, etc)
• Examine feasibility of Java 17
  • BACKGROUND: a small number of LexEVS components (aka dependencies) are being phased off of java 8 (or are no longer being supported on java 8).  We ideally want to use a current version of those components (dependencies). IF the current version of that component is only supported on Java 14 or later (just as an example), then we would have to migrate the ENTIRE LexEVS stack to Java 14 or later. (Note that the current Java version is Java 21 LTS, and the most popular non-LTS version is Java 14). So there is a risk that a vulnerability is found in the older version of the component/dependency and we would have to either migrate everything quickly to a new version, or not use that component (which might not be possible), or shutdown LexEVS entirely. Note that there are certain versions of Java which are "long-term support" versions - meaning that they will be supported for several years beyond non-LTS versions. LTS versions are Java 8,  Java 11, Java 17, and Java 21.
  • OBJECTIVE: find out what would it be like to upgrade from Java 8 LTS to Java 17 LTS.  How hard would it be? How long might it take?
  • LEXEVS-5361- Investigate Java 17
• Miscellaneous bug fixes (several small bugs that have been identified over time and need to be addressed)
  • EVSREPEXP-491 resolve branch-download list not being displayed on chrome browser (now FIXED)
  • EVSREPEXP-433 Security issue: set-value vulnerability (in progress)
  • LEXEVSCTS2-452 test_associations_subject_of call revealed hierarchy bug
  • EVSREPEXP-478 Feedback form is not coming up
  • LEXEVS-5252 Read an Entity by URI throwing a 302 error
  • LEXEVSCTS2-431 Service resource does not populate Service name/version
  • Investigate ERROR messages (both reported by Jason Lucas, and in catalina.out )

ACTIONS

•  Benson, Mark (NIH/NCI) [C] to add JIRA ticket to debug error messages found during outage to Sprint 213
  

LexEVS Code Debt Refactoring

• Coding complete on lexevs services - except for isolated dependencies
  • The isolated dependencies largely depend on using an updated version of Java (e.g. they are using more current Java versions. Java 21 LTS is the current version.  The more popular non-LTS Java version is Java 14)
  • Scott is investigating costs and feasibility of Java 17 (see LEXEVS-5361 above)
  • LEXEVSCTS2-447 javax-servlet - on hold, until we update Java 17
  • LEXEVSCTS2-446 spring-boot - on hold, until we update Java 17
• Work on NCIt Browser - ehcache beta on dev. Kim approves promotion (Scott)
• • updated version of Java (e.g. they are using more current Java versions. Java 21 LTS is the current version.  The more popular non-LTS Java version is Java 14)
  • Scott is investigating costs and feasibility of Java 17 (see LEXEVS-5361 above)
  • LEXEVSCTS2-447 javax-servlet - on hold, until we update Java 17
  • LEXEVSCTS2-446 spring-boot - on hold, until we update Java 17
• Work on NCIt Browser - ehcache beta on dev. Kim approves promotion (Scott)