A Note on Version Numbering
There are times when I have seen projects with a version 1.9 that means “the last 1.x release before 2.0″. In our case, “1.9″ simply means “the release after 1.8″
After a bit of discussion on the liquibase-user mailing list, we decided that we didn’t want to go to a 2.0 release at this point because there has not been any major changes and we have kept backwords compatibility.
Therefore, we are going to continue our current 1.x numbering strategy and continue to provide evolutionary improvements for the foreseeable future. 1.10, 1.11 etc. do look a bit confusing and like 1.1.0, 1.1.1 etc, but I think most LiquiBase users will be smart enough to figure it out 
Nayan Hajratwala:
That’s how Maven version numbering works as well, so at least the Maven users will have no problems with it.
12 January 2009, 3:44 pmCarsten Lenz:
I think that’s simply logical. It makes no sense to “allow” just ten Version between 1.0 and 2.0 (1.0-1.9)
21 January 2009, 11:23 amBy the way, that also how we manage version numbers with our governmental client.