Issue Tracking
This page descries how we track issues in the liquibase repository.
We use github Issues and PRs to track and process work.
The Liquibase Community team watches that queue and moves the item to the Liquibase Community Org Project (beta) for initial triage, assignment, and processing.
Please search the open issues/PRs as best you can prior to opening a new issue. If you have a question/concern related to a closed issue/PR, please open a new issue and reference the closed one. This will help us make sure your request gets reviewed and addressed.
We are in the process of maturing this board to better indicate how everyone can best help move issues and PRs along through the process. Stay tuned.
As tickets are set to be included in a release, we will set the milestone to NEXT to indicate the NEXT planned release.
If a PR does not require a release, no milestone will be set and the Requires Release field in Liquibase Community Org Project will be set to REL-N.
When a PR is released, we will set the milestone to the actual release number.
Talk to us on the Liquibase Forum, Liquibase Discord, or
clone it at https://github.com/liquibase/liquibase.wiki.git and create an issue with a patch file.