Just a reminder that the 2018 Liquibase Community Survey is still open through April 14th.
Listening to feedback from the community is a vital part of any open source project and it has frankly been a little too long since I’ve had the chance to hear the voice of those who make use of Liquibase. As I make more time to devote to the project, I’m keen to understand your perspective – if nothing else, to inform my priorities as I go through pull requests and think through additional updates.
For those of you not watching the download page every day, Liquibase 3.5.5 was released on Feb 15th.
After far too long, the Liquibase-Hibernate plugin has been updated to support Hibernate 5.x!!
The issue that caused me to pull the 3.5.2 release turned out to be a false alarm.
Unfortunately, we found a major issue with the 3.5.2 release and so I am removing it from the download page. A new-and-improved 3.5.3 release should be out in the near future.
Bugfix release Liquibase 3.5.2 is now available from liquibase.org/download and through the Maven repositories.
Ten years ago, I started Liquibase to bring sanity to my database schema changes. At the time, I was working on a 3-tier Java web project. Ruby on Rails had Active Record Migrations and I asked, “Why can’t I have that for Java?” Since then, Liquibase has become the standard for database change management. We support 13 databases and have 24 extensions for other databases. (Hi, Teradata and Hana!!!) All of that progress is because of our amazing users, committers, and testers. We couldn’t have done it without you.
Liquibase has always focused mainly on “standard” SQL databases, but we are looking to improving support for NoSQL databases like Cassandra, MongoDB, Hadoop and others. We’d also like to make sure our support for databases like DB2 on iSeries and System z as well as Redshift, Azure SQL Server, Vertica, Greenplumb etc.