Jun 12, 2026, 8:15 AM
This commit is contained in:
@@ -7,3 +7,24 @@ Status: Active
|
||||
---
|
||||
|
||||
Dzisiaj ogarniam rzeczy związanych z kontami i restorami, nie mam dzisiaj nic specjalnego do zapisania, pracuję dzisiaj do godziny 13:30
|
||||
|
||||
|
||||
Meeting notes
|
||||
Database management
|
||||
|
||||
Paweł expressed concerns about the quality of scripts produced by Shivangi and highlighted risks of disabling constraints in the Picard database.
|
||||
Paweł discussed the complexity of the Picard database and warned that improper changes could lead to a production crash.
|
||||
Adrian confirmed that backups will be performed before each release, and a rollback plan will be in place to mitigate risks
|
||||
Adrian clarified that development responsibility lies with Shivangi, Luca, and their team, while Radek is accountable for overall risk
|
||||
Adrian suggested that, in case of failure, Radek's team could consider bringing Guido back as a consultant to help redevelop the solution
|
||||
Grzegorz reported that they reduced the number of access and disk overload tickets from 23 to 12, completed database clean-up tasks, and finished their part of the Visma project backup.
|
||||
Grzegorz shared that a new MySQL update for production in Norway is expected in the coming weeks, and they are preparing scripts to switch the availability group to another node.
|
||||
Release planning
|
||||
|
||||
Adrian informed participants that production patching in the Nordic market will pause during July, with patching scheduled for June and August, while other markets will continue as normal.
|
||||
Follow-up tasks
|
||||
|
||||
Task Assigned to Due date Bucket
|
||||
Talk to Radek during the next meeting about the potential risks in Picard production (Adrian)
|
||||
Paweł proposed reviewing Shivangi's scripts together to identify potential issues and improve their quality (Paweł, Adrian)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user