The numbering would be like 1.6.3 , 1.6.4 etc. until there is a version that is very different in backward compatibility when it switches to 1.7.0 and carries on from there. If there is a real need to issue a maintenance release 1.6.5 afterwards, it will be done. Quite similar to JDK releases.
For continuity, the next point release will be 1.6.2 unless we do introduce a different file format that is not backward compatible (unlikely at the moment). Fred Toussi ----- Original Message ----- From: "Clay Lenhart" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: 15 December 2001 22:57 Subject: Re: [Hsqldb-developers] HSQLDB version numbering. Fred Toussi wrote: >We used this numbering scheme because it was used in the HypersonicSQL >project (version 1.43 was not the 43rd release in the 1.x series, was it?) > >Personally, I would prefer 1.6.1 , 1.6.2 , etc., where we go up from 6 to 7 >when we introduce a file format that is not backward compatible, or >improvements that are likely to break SQL statements. written against the >previous version. > >Fred Toussi > I like the 1.6.1 scheme too, however I do not want to confuse users. I.e. does 1.63 come after 1.7? In the 2.x series, lets switch to the 3 number scheme, but for th 1.x series, lets stick with the same scheme. -Clay _______________________________________________ hsqldb-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hsqldb-developers _______________________________________________ hsqldb-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
