Development

With the release of Emilda 1.2-alpha, the 1.2 branch has reopened and we are accepting new features/commits. We urge everyone to try out the new 1.2-alpha release and report any bugs you may find. As the stable release of 1.2 is coming closer, we can't accept new features for long so if you have something on your mind share it on the mailing lists or on IRC.

The main trunk of Emilda 1.2 has undergone big changes today. Since important features require large modifications, the MySQL table structure has changed again. For the time being, You have to manually find the differences in the emilda.sql file and update Your database; I'm trying to find some time to write a small script that would perform these changes automatically, or at least generate a file that could be directly imported into MySQL, containing the appropriate changes. More on this later, for now, please rely on 'diff' =)

One of the big features added today is the implementation of the fining system, and in conjunction with this, the finalisation of the "Item Types"-system. This system does, however, still lack some features, such as having location specific item types, so that each instance can have custom Item Types, suitable for the instance in question.

Emilda 1.2 (unstable) has undergone one of the big changes that were scheduled in this release: all configuration has been moved into MySQL. What this implies, is that the files 'config', 'MARC_config' and 'MARCsyn_config' are obsolete, and replaced with equivalents in MySQL (tables 'configuration' and 'marc_configuration')

What each user using the latest unstable version needs to do, is to update the MySQL table structure to get the latest version to work. The tables 'configuration' and 'marc_configuration' need to be added, and populated with the data supplied in emilda.sql from the 'sql' module in CVS.