📢 Flyway Community DB Support moving to https://github.com/flyway/flyway-community-db-support

[Barry-RG]

As many of you are probably very aware, Flyway has an issue in regards to its lead time in merging PRs from the community.

This is due to a hardcoded build mechanism that we use to deploy to flyway/flyway which has been there since Flyway's early releases and which we have not been able to move away from. Over the last couple of years the use of this system has become a hindrance and prevented us from interacting with our open source PRs in the way that we would wish. As a result, we are looking at ways to improve this in a method which does not significantly disrupt Flyway development.

The flyway/flyway-comunity-db-support repository is one of those ways.
since database contributions are normally the most self contained. As a result, we have migrated the flyway-community-db-support module and its children to this repository from flyway/flyway to allow us to more quickly and directly interact with contributions and requests from the community without the barriers we have had before.

We understand that doing this on a non-major release may be a surprise, but we felt getting a pipeline that allowed Flyway to work better as an open source project was more important.

However, this does mean that any currently open PRs for Database support will have to be migrated by their owners to flyway/flyway-comunity-db-support. We have not wanted to make this announcement earlier so that migrated PRs did not seem to ignored once that reached their new destination.