These decisions were originally made by the Tech Leads group. As part of a consolidation effort, they have been migrated to the newer Technical Council's Decision Log. The decisions have been moved here to maintain history, comments, original context, etc.

How to coordinate introducing API compatibility breaking changes?
How to improve/simplify release proces?
System and Tenant-level Users
Tenant Id and Module Name Restrictions
Handle i18n where messages are generated
Karate API Integration Tests Implementation Guidelines
Deletion of core-module records may leave dangling references from non-core modules
Data export by using Spring Batch (aka Export Manager)
Optimistic locking support
Log4j2 is the recommended logging library for all core java modules
Should build (pom.xml) changes required by new RMB be considered breaking?
Teams must document deployment requirements in a clear & consistent way
Apache Kafka usage in inventory-storage
Use of Testcontainers for test infrastructure
Spring Way Equivalent of Edge-common
Upgrade to JDK 11
UI Testing approach
Platform agnostic object storage for Exports
Personal Data Disclosure Process
Include instance id in the inventory-storage notifications for items
Localization parameter for back-end
Teams to implement UI end to end integration tests
FOLIO should define a minimal platform

Migrated Decisions