NOTE: Detailed notes weren't captured for today's meeting. For the most part the time was spent reviewing the Kanban board. We left comments on several JIRAs, but nothing worth explicitly noting here.
We need to communicate the expectation better - e.g. add something to the platform release notes indicate how long P1 security issues will be backported to that release.
As long as we upgrade to the latest LTS release of Spring Boot in each flower release, we should be in decent shape - only ~1 mo. where we're running a version of Spring boot that's no longer supported.
Note that we're currently a bit behind with this, even if we upgrade edge modules, etc. in a Lotus HF, kiwi and Juniper will be running older, unsupported versions for some period of time. Going forward we'll need to be diligent about this to avoid getting into this situation again.
Today:
The conversation about what we want to say has not happened yet.
5 min
Update on
Jira Legacy
server
System Jira
serverId
01505d01-b853-3c2e-90f1-ee9b165564fc
key
FOLIO-3317
Axel
Axel Dörrer Should be removed from week to week agenda and Axel will monitor for progress and report back
ui-test:94 Was merged, a problem was reported, leading to this being reverted.
Appears to be an environmental problem.
The JIRA is now unassigned... it isn't clear who has the ball here.
Added a comment to STCLI-190 tagging Khalilah, Ryan, and Zak
This PR has been reverted because of issues with the included changes of kopy version. The idea is to exclude the kopy changes by now to move forward with this.
Last week:
No movement, but a PR should be coming soon.
Conversations are ongoing within the Stripes Arch. group.
Maybe replace kopy with something else that's better maintained
Maybe roll our own replacement
Today:
No significant movement. Check in next week.
5-10 min
Jira Legacy
server
System Jira
serverId
01505d01-b853-3c2e-90f1-ee9b165564fc
key
MSEARCH-357
Team
have we heard anything from the mod-search devs on this? Is it possible to use the openSearch client, or possibly make it configurable which client is used?
ALL to figure out exactly what we want to say about backporting security fixes and get it added to the Morning Glory release notes wiki page. (To be discussed in Slack)
Craig McNally to cleanup the remaining upgrade to vertx-4 stories → P2, Morning Glory, security-reviewed. A comment was already left on the parent Epic.