The CVS repository structure for the project needs to be streamlined and simplified. This process was delayed until changes to the Licence text were finalised in the beginning of March. As we are approaching the final release of 1.7.0 and in order to kick-start the development of 1.7.1 and accommodate the more recent patches we need to take action as quickly as possible.
In December last year, a plan was developed by Jason Van Zyl with my input which broadly follows well established CVS structures. This plan, as updated to reflect code developments since then, is as follows: i) lay down the original hsql source and create and HSQL_1_4_BRANCH and tag it as HSQL_1_4_3 and this is where the original source will always remain. ii) lay down the reformatted 1.43 codbase (reformatted according to Java code guidelines and Java Doc and Licence comments are added using only automated software tools) over i) and tag this as HSQL_1_4_4. This will be used for comparison with hsqldb 1.60 for source changes. I have experimented with this on a few files and the resulting files are fairly easy to compare with 1.60. iii) lay down the 1.60 source over top of ii) and create a branch HSQL_1_6_BRANCH and tag this as HSQL_1_6_0. (the first HSQLDB release). iv) lay down the 1.61 source over top of iii) and tag this as HSQL_1_6_1. (the second HSQLDB release) v) lay down the 1.7.0 source over top of (iv and that will be our trunk of HEAD. The hsqldb-dev2 directory on the CVS follows the above plan but the contents need updating to reflect changes to the license and changes to the directory structure to reflect the 1.7.0 distribution. This directory structure is as follows (the srctest is not in the RC3 distribution and will be added to contain jUnit tests for the HSQLDB internals): bin build demo doc lib src srctest The purpose of this is to have a simple CVS structure. It is also possible to have an additional, parallel directory in the CVS which contains ONLY final public releases of the HSQLDB and is updated only by the project admin. This could perhaps act as a safety mechanism against mistakes by developers who commit to the CVS. If you have used, or want to use the project CVS, please comment. I would like to have a structure that is simple to understand and use both for end users and for developers. I have also posted this to the Open Discussion Forum. Fred Toussi _______________________________________________ hsqldb-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
