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.
Julian Ladisch has created a few JIRAs for this – he's still working on this.
He also wrote a script to list the affected modules - runs periodically
The edge modules are probably the most critical - 3 of them are affected. The related POs are aware.
Should these fixes be backported to Kiwi?
Prevailing thought is that it should since Kiwi is the latest release and Lotus isn't official yet.
Craig McNally will communicate this recommendation to the Capacity Planning group, and possibly Oleksii Petrenko.
Additional communication will be made once the path forward is clear.
Discussed with Mark V. Harry K, and Oleksii P. - Aiming for Lotus (HF) and Morning Glory.
Still confusion about how many releases need to be supported, LTS, etc.
Note that this is a P3, if it were a P1/P2 the decision might have been different.
Today:
The priority for some of these stories (specifically edge APIs and the umbrella story) has been bumped to P2
This was done so that the fixes can be included in a Lotus hot fix
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
Today:
Continue discussion from slack... Spring Boot LTS
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:
R1 releases have only ~1 mo. where we're running a version of Spring boot that's no longer supported.
R2 releases are fully covered (4 months with security support)
R3 releases have ~3 months 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.
5 min
Update on
FOLIO-3317
-
Getting issue details...STATUS
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.
Today:
Conversations are ongoing within the Stripes Arch. group.
Maybe replace kopy with something else that's better maintained
Check in on
MSEARCH-357
-
Getting issue details...STATUS
next week.
Action items
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.
