Agile development practices and modern source control systems such as Git have transformed how application software is developed and managed. But for many application developers the way the database is changed is the same as it was in 1995. Well, maybe not exactly the same—now SQL files for each release are stored in a shared Windows drive instead of a shared Novell server – but you catch my drift.
Bugfix release Liquibase 3.5.1 is now available from liquibase.org/download and through the Maven repositories.
In the modern agile development environment there is a lot that happens in a very short period of time. This means application release managers need to be efficient with their time while ensuring nothing falls through the cracks. The database updates that go along with each application release are just as important as the application code, both for deployment and for planning rollbacks.
As a QA team member, you always make sure you are testing the current version of an application. However, it is just as important that the testing schema is correct and that there are no unexpected changes that the developers have applied to their environment that you do not know about.
Bugfix release Liquibase 3.4.2 is now available from liquibase.org/download and through the Maven repositories.
Halloween–the spookiest night of the year. Spookiest night for those who don’t do production deployments anyway…
There were 136 responses to the 2015 Liquibase Survey. Since I’m relying on self-selection for people answering the survey, the first question is how representative is the data. The only two “demographic” survey questions I have alternate data points for are version used and country.
Early on, Liquibase only supported XML changelogs with each changeSet listed in it. There are many advantages to using that setup, but there are now many different ways to store your database changes.
If you missed last month, I’ve started a monthly status post to give a better window into Liquibase development and the Liquibase community. I’d appreciate any feedback you have on how helpful (or not) it is and/or any suggestions you have.