> I also recall being "confused" by fact that "minor" version increments > are the ones that break compatibility, not just the major ones... if > you are using PG anyway :-)
It's all terminology. PG defines "minor" as the version at the third place. So for PG a minor version upgrade is 8.4.1 to 8.4.2 and that will never introduce new features nor will it break compatibility and will never change the on-disk layout. A "major" upgrade is either the first or second digit (8.3 -> 8.4, or 8.4 -> 9.0) I think H2 could profit from something similar. Anyone who is using H2 in a production environment must have a way to use a bugfix release that is guaranteed to not break anything (read: not change existing functionality, not change on-disk layout, not change existing API) How that is reflected in the numbering is a completely different thing. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
