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.
Update? Have we added anything to the MG release notes?
Not yet... Craig McNally will refresh his memory on what we agreed to at previous meetings and will send out a strawman message in the slack channel for review.
Today:
Textproposal:
Morning Glory will receive security fixes for critical issues until Orchid is released (est. Spring 2023). Detailed information on particular issues will be provided by the security team. With this release there will be no other security hotfixes on Kiwi.
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
Axel Dörrer waiting to hear back from Ann-Marie B. about the data-import ticket ... maybe target Nolana?
Today:
Leipzig Devs mentioned that filling up memory can not only be solved by a limit on uploads. It also should consider multiple simultainous uploads as scenario.
Axel Dörrer to check back with dev what other possibilities of implementation could be.
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?
Today:
Seems to be possible to migrate to OpenSearch. Might be moved higher in the Spitfire Backlog
Last week it was noted that there was a slack conversation started about this. Need to check in on Oleksandr Bozhko's progress (he's was investigating the problem.
no news in the last 7 days... Craig McNally to nudge him and see where this stands.
Today:
Open PR on FOLIO-3448 (Documentation as a warning for developers)
Craig McNally to check if a new Jira has to be created for that and push on that
5 min
edge-lti-courses
Team
edge-lti-courses has been unmaintained since July 2021. Open Jiras:
There are several JIRAs on our board that haven't moved in a long time (well over a year in some cases...)
Do we want to possibly close these as won't do?
Craig McNally to look into how we can sort the board by last updated date, making it easier to see what's been lingering
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)