From 58af850f50e8b15eb5d188e417bfb5c922d61f97 Mon Sep 17 00:00:00 2001 From: Sun Cao Date: Mon, 16 Nov 2026 18:27:50 +0000 Subject: [PATCH 1/2] Say how a host that supplies its own Transactions gets OpenSharing's schema The Flyway migrations and JpaTransactions ship only in opensharing-server, so a host that embeds opensharing-server-core with its own Transactions has to create the tables itself. RELEASE.md said a host must not. Co-authored-by: Isaac Signed-off-by: Sun Cao --- RELEASE.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 08e84f45..28f87e66 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -48,9 +48,12 @@ From 1.0.0, the server artifacts follow semantic versioning: - **MINOR** — additive and compatible with earlier 1.y.z releases. - **PATCH** — compatible fixes only. -The database schema is created and migrated by Flyway on startup (see -`JpaTransactions`), and a schema change is a new migration for every supported -database. A host must not create or alter OpenSharing's tables itself. +The standalone server creates and migrates the database schema with Flyway on +startup (see `JpaTransactions`), from the migrations in `opensharing-server`'s +`db/migration`. A schema change is a new migration for every supported +database. A host that supplies its own `Transactions` creates OpenSharing's +tables in its own migrations, exactly as those migrations define them, and adds +each new one when it upgrades. It must not change the tables in any other way. ## Release process From 9e497b49145dd7609c1bf2eabfabe732a1fe5f42 Mon Sep 17 00:00:00 2001 From: Sun Cao Date: Mon, 16 Nov 2026 18:31:06 +0000 Subject: [PATCH 2/2] Drop the extra sentence about changing the tables Co-authored-by: Isaac Signed-off-by: Sun Cao --- RELEASE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RELEASE.md b/RELEASE.md index 28f87e66..d3bd7c97 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -53,7 +53,7 @@ startup (see `JpaTransactions`), from the migrations in `opensharing-server`'s `db/migration`. A schema change is a new migration for every supported database. A host that supplies its own `Transactions` creates OpenSharing's tables in its own migrations, exactly as those migrations define them, and adds -each new one when it upgrades. It must not change the tables in any other way. +each new one when it upgrades. ## Release process