As Radiance, and modules built on it, evolve, certain breaking changes will from time to time be necessary (#29). In order to accommodate this, and in order not to break existing setups, a migration facility should be introduced.
This facility should keep track of versions of used modules, and automatically trigger a function that can perform migration steps when a version change occurs. This migration should be run as part of Radiance's startup sequence, and should probably be coded something like this:
Calling this function will need a bit more setup however, in order to not skip versions when the change is between multiple concrete versions. So for instance if there are versions 1.0, 1.1, and 2.0, but the change happens from 1.0 to 2.0, migrate should be called with both 1.0 1.1 and 1.1 2.0.
By letting from-version be NIL if the module has not been installed previously we can also alleviate issues such as new default permissions not being applied for new users.
As Radiance, and modules built on it, evolve, certain breaking changes will from time to time be necessary (#29). In order to accommodate this, and in order not to break existing setups, a migration facility should be introduced.
This facility should keep track of versions of used modules, and automatically trigger a function that can perform migration steps when a version change occurs. This migration should be run as part of Radiance's startup sequence, and should probably be coded something like this:
Calling this function will need a bit more setup however, in order to not skip versions when the change is between multiple concrete versions. So for instance if there are versions
1.0,1.1, and2.0, but the change happens from1.0to2.0,migrateshould be called with both1.0 1.1and1.1 2.0.By letting
from-versionbe NIL if the module has not been installed previously we can also alleviate issues such as new default permissions not being applied for new users.