Participating modules:

• BOM
• SPI (0.8.5)
• Pool (0.8.7)
• SQL Server (0.8.6)
• Postgres (0.8.8)
• Proxy (0.8.6)
• MariaDB (1.0.1)
• Spanner (0.5.0)

With joining the Reactive Foundation, we should ensure DCO rules so that contributors certify they have the right to submit contributions.

We should enable https://probot.github.io/apps/dco/ and update the contribution guide. Also, we should mention that R2DBC is a Reactive Foundation project.

Since the r2dbc-module.version property was removed and each module is configured manually, no need to set this in the create-release.sh script.

R2DBC H2 isn't maintained currently and hasn't upgraded to R2DBC 0.9.

Participating modules:

• Postgres
• SQL Server
• BOM

Participating modules:

• Postgres 0.8.12.RELEASE

• SPI 0.8.2 r2dbc/r2dbc-spi#171
• Pool 0.8.3 r2dbc/r2dbc-pool#70
• H2 0.8.4 r2dbc/r2dbc-h2#164
• Postgres 0.8.3 pgjdbc/r2dbc-postgresql#280
• SQL Server 0.8.3 r2dbc/r2dbc-mssql#153

Participating modules:

• BOM
• Pool (0.8.6)
• Proxy (0.8.5)
• Postgres (0.8.7)
• MariaDB (1.0.0)
• Spanner (0.3.0)

With the migration from the R2DBC org to the Postgres org, r2dbc-postgres changed its groupId from io.r2dbc to org.postgresql.

Participating modules:

• Postgres 0.9.2.RELEASE
• R2DBC Pool 0.9.2.RELEASE
• R2DBC Proxy 0.9.1.RELEASE
• MariaDB 1.1.2

Participating modules:

• SPI (0.8.6)
• BOM
• MariaDB (1.0.2)
• SQL Server (0.8.7)
• Postgres (0.8.9/0.8.10)
• Proxy (0.8.8)
• Spanner (0.6.0)

Artifact coordinates:

<dependency>
  <groupId>org.mariadb</groupId>
  <artifactId>r2dbc-mariadb</artifactId>
  <version>0.8.3-beta1</version>
</dependency>

Feature Request

To prevent future use of SNAPSHOT-Dependencies (see #31) you could use Maven Enforcer Plugin

Is your feature request related to a problem? Please describe

We tried using Spring Boot 2.3.1 and our Build failed because of the enforcer rule mentioned below...

Describe the solution you'd like

Maven Enforcer Plugin Rule should be configured in pom.xml

Describe alternatives you've considered

Overriding r2dbc-bom.version in our pom.xml, see Spring Boot Issue #22083

Teachability, Documentation, Adoption, Migration Strategy

see Enforcer rule Require Release Dependencies

Participating modules:

• Postgres 0.9.1.RELEASE

We should add the MySQL driver dev.miku:r2dbc-mysql to the BOM.

We should consider repurposing the BOM for R2DBC dependency management for SPI and drivers. The idea is that we maintain a BOM release train per minor version (0.8 -> Arraba, 0.9 -> B, …). Compatible driver versions from the R2DBC organization and from the community are maintained with the BOM for easier consumption.

The BOM would release service release updates (Arabba-SR1, Arabba-SR2, …) for each increment that is either driven by the SPI or by driver updates on a regular basis (every 2-3 months)

Arabba-SR4 uses r2dbc-proxy 0.8.3.BUILD-SNAPSHOT
https://github.com/r2dbc/r2dbc-bom/blob/Arabba-SR4/pom.xml#L41
As a result, build fails with Arabba-SR4 if using r2dbc-proxy and https://repo.spring.io/snapshot is not configured.

Is this intentional or accidental?

R2DBC aims to stay lean and does not want to ship its own client implementation as R2DBC is a specification for an SPI along with a few reference implementations. We don't want to get into client business ourselves but we see R2DBC as an enabler for the client eco-system.

Therefore, we should remove R2DBC Client from the BOM.

Spanner will be released once the specification is GA.

Participating modules:

• BOM
• Google Cloud Spanner 1.1.0
• MariaDB 1.0.3
• H2 (0.8.5)
• Postgres (0.8.11)
• Pool (0.8.8)
• • SQL Server (0.8.8)

Participating modules:

• BOM
• r2dbc-proxy 0.8.3
  • need 0.8.3 release with dependency updates(spi and reactor)
• r2dbc-mssql 0.8.5
• r2dbc-postgresql 0.8.6
• r2dbc-pool 0.8.5

Bug Report

Arabba-SR4 can't be used for r2dbc-proxy without either relying on a SNAPSHOT version (0.8.3.BUILD-SNAPSHOT is in the BOM) or explicitly overriding the version of r2dbc-proxy.

See:

https://github.com/r2dbc/r2dbc-bom/blob/Arabba-SR4/pom.xml#L41

I realise SR4 can't be updated, but please keep us non-snapshot cowards in mind for SR5 :)

Participating modules:

• BOM
• Postgres 0.8.5
• Pool 0.8.4

A BOM should not have a list of repositories as each consumer of the BOM should make sure to add the relevant repo (be it the recommend one or some corporate proxy, etc).

Ideally these should be removed.

R2DBC MySQL isn't maintained currently and hasn't upgraded to R2DBC 0.9.