Septuro

In the Septuro Builder I created a folder called mysql. This folder holds the exports of the creation of the database and the export of each table associated with and object in the same name spaces as the objects themselves. I was thinking that each time there is a change to a database or a database table to do a export, then copy that export to the mysql folder for the application. This way subversion itself will be the version control for the database. I talked to Steve Phillips about this and he thinks that each change to the database be appended to the end of a database version control file. The main thing we need it to know is the state of the database at any version of an application in the past.

Septuro has now switched completely to a subversion repository. We began this project using CVS due to familiarity, but all of us developers have had an interest in subversion for some time. The switch was completed yesterday evening and two branches are available for checkout and browsing.

/trunk is, as any subversion user will guess, the main trunk of the project. We are using a strict branching system, so /trunk should always be stable and usable.

/branches/form is a branch that will be used to create the form module and form object that will power any form on the entire system, in any application. Once completed, it will be rolled back into /trunk.

Right now, there are no releases or tags, but you can be assured that as soon as we have some, we will let you know.