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.
Time
Item
Who
Notes
Official security support policy on releases
Security team needs
How many releases from now has to be supported? (3-4 releases or less?)
Priority/Risk will likely factor into this as well.
Also a matter of capacity
Should be raised to the PC → Axel can bring this with a paper/proposal to the PC - not yet.
Probably want to bring this to the TC as well at some point, even if only for awareness.
WOLFcon session?
Axel will produce a paper that outlines that problem by next weeks meeting.
Chris to ask his stakeholders about TAMU needs - not specifically, but has started to have some conversations
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:
Update? Have we added anything to the MG release notes?
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:
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?
5-10 min
Jira Legacy
server
System Jira
serverId
01505d01-b853-3c2e-90f1-ee9b165564fc
key
MODEXPW-67
/
Jira Legacy
server
System Jira
serverId
01505d01-b853-3c2e-90f1-ee9b165564fc
key
MODEXPS-109
/
Jira Legacy
server
System Jira
serverId
01505d01-b853-3c2e-90f1-ee9b165564fc
key
FOLIO-3448
Team
Has there been any progress here?
Last week it was noted that there was a slack conversation started about this. Need to check in on Oleksandr Bozhko's progres (he's was investigating the problem.
Today:
5 min
edge-lti-courses
Team
edge-lti-courses has been unmaintained since July 2021. Open Jiras: