You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Going forward, R2DBC 1.0 is expected to become the "done" version and a baseline for drivers for the foreseeable future. Having a bill of materials during the specification evolution helped to correlate driver versions to the specification version to ensure a consistent dependency arrangement.
With version 1.0 of the specification, we expect all available drivers to be based on that version which removes the need for version coordination. Additionally, BOM releases enforce a strong synchronization across participating drivers and BOM releases require constant release effort.
Therefore, I propose to stop releasing the BOM after the last 0.9 R2DBC release train, likely during the next year.
The text was updated successfully, but these errors were encountered:
Going forward, R2DBC 1.0 is expected to become the "done" version and a baseline for drivers for the foreseeable future. Having a bill of materials during the specification evolution helped to correlate driver versions to the specification version to ensure a consistent dependency arrangement.
With version 1.0 of the specification, we expect all available drivers to be based on that version which removes the need for version coordination. Additionally, BOM releases enforce a strong synchronization across participating drivers and BOM releases require constant release effort.
Therefore, I propose to stop releasing the BOM after the last 0.9 R2DBC release train, likely during the next year.
The text was updated successfully, but these errors were encountered: