Liquibase 是否仍在积极开发？
Is Liquibase still active in development?
我在 Github 看到最后一次提交是几个月前完成的，最后一次发布是从 2016 年开始的。如果项目仍然有效，有什么想法吗？
Liquibase 仍在积极开发中。这是来自 Liquibase-Developers forum, dated November 13, 2017.
的 post
Hi,
It's always great to hear from people who find value in and who are
actively using Liquibase. I can take a moment to provide some updates
regarding the future plans for Liquibase.
To be fully transparent, as of late, I’ve been very committed to other
projects and have not been able to make time to contribute to
Liquibase. This isn’t how I want things to go, and I agree that
updates on Liquibase are overdue. To directly address your question,
we do have a plan to push out a release that includes a number of high
value pull requests that are currently sitting in review. In all
honesty, this is something that will be out early next year (likely in
January) as I simply don’t have many spare cycles right now.
Going forward, I know that both myself and the broader team at Datical
know we need to do more to keep the Liquibase project moving forward.
It’s common for open source efforts to sometimes stagnate or slow, but
we certainly don’t want things to come to a halt. As such, you can
expect more active maintenance and involvement than there has been of
late.
In regards to the the Datical fork, it's not really a fork but simply
a branch which will get merged in when I get a chance to make sure it
is does not include any changes that will adversely affect other
Liquibase users. It will be brought in as part of the 3.6 release.
Lastly, we are spending some time thinking about how we can add more
committers to the Liquibase project. When I do get busy, I don’t want
to continue to be the sole bottleneck to progress on this project. I
don’t have a vetted strategy yet, but I’d look to active, engaged
members from the user community to step up and serve as committers.
The DBManul merge was a good example of this where a community member
was able to go through the work of testing and integrating a large set
of pull requests that I was able to bring in a bundle. That was very
helpful, but we need something more consistent and organized. As the
project and community has grown over the years it has become well past
time that I found ways to scale process of accepting pull requests.
Thanks again for being an active user for all these years. I
appreciate you sticking with this project, and I hope that you (and
others that a part of the Liquibase community) remain with us as we
bring development of Liquibase back to a more predictable pace.
Nathan
我在 Github 看到最后一次提交是几个月前完成的，最后一次发布是从 2016 年开始的。如果项目仍然有效，有什么想法吗？
Liquibase 仍在积极开发中。这是来自 Liquibase-Developers forum, dated November 13, 2017.
的 postHi,
It's always great to hear from people who find value in and who are actively using Liquibase. I can take a moment to provide some updates regarding the future plans for Liquibase.
To be fully transparent, as of late, I’ve been very committed to other projects and have not been able to make time to contribute to Liquibase. This isn’t how I want things to go, and I agree that updates on Liquibase are overdue. To directly address your question, we do have a plan to push out a release that includes a number of high value pull requests that are currently sitting in review. In all honesty, this is something that will be out early next year (likely in January) as I simply don’t have many spare cycles right now.
Going forward, I know that both myself and the broader team at Datical know we need to do more to keep the Liquibase project moving forward. It’s common for open source efforts to sometimes stagnate or slow, but we certainly don’t want things to come to a halt. As such, you can expect more active maintenance and involvement than there has been of late.
In regards to the the Datical fork, it's not really a fork but simply a branch which will get merged in when I get a chance to make sure it is does not include any changes that will adversely affect other Liquibase users. It will be brought in as part of the 3.6 release.
Lastly, we are spending some time thinking about how we can add more committers to the Liquibase project. When I do get busy, I don’t want to continue to be the sole bottleneck to progress on this project. I don’t have a vetted strategy yet, but I’d look to active, engaged members from the user community to step up and serve as committers. The DBManul merge was a good example of this where a community member was able to go through the work of testing and integrating a large set of pull requests that I was able to bring in a bundle. That was very helpful, but we need something more consistent and organized. As the project and community has grown over the years it has become well past time that I found ways to scale process of accepting pull requests.
Thanks again for being an active user for all these years. I appreciate you sticking with this project, and I hope that you (and others that a part of the Liquibase community) remain with us as we bring development of Liquibase back to a more predictable pace.
Nathan