Implement a migration system #31
Conversation
…n always log even before init.
…ance is already running.
…me more information about what's going on.
…directory instead. See Shirakumo/radiance#31
documentation.lisp
Outdated
| See VERSION<=") | ||
|
|
||
| (function version-bounds | ||
| "Returns a subsequence of VERSIONS that is bounded by start and end. |
There was a problem hiding this comment.
I think the first description lines of version-region and version-bounds could use some work. If I understand correctly, version-region returns essentially (<= start x end), and version-bounds returns that same subsequence, but ensures it starts with start and ends with end?
Maybe something like this for version-region:
Returns the versions in VERSIONS that are between START and END, inclusive.
And something like this for version-bounds:
Returns the versions in VERSIONS that are between START and END, inclusive, ensuring the sequence starts with START and ends with END, if provided.
documentation.lisp
Outdated
| T --- The system is migrated to its current system version. | ||
| version --- The system is migrated to this specific version. | ||
|
|
||
| When this function is called it determines the list of effective |
There was a problem hiding this comment.
I think "effective" should be replaced with "concrete", which is what it's called everywhere else.
defaults.lisp
Outdated
| @@ -228,3 +228,29 @@ | |||
| (T | |||
| ;; Other refer, no change. | |||
| )))))) | |||
|
|
|||
| ;;; Default logger to make sure we can log even before the real impl is laoded. | |||
|
Went through the changes. It seems like a really solid and sensible system to have. If there were any issues, they escaped my eyes and I didn't catch anything wrong with the documentation either. All in all |
…ntation definitions. Should fix some upgrade weirdness, I hope.
…directory instead. See Shirakumo/radiance#31
…directory instead. See Shirakumo/radiance#31
This implements a relatively simple migration system for Radiance and its users that allows the migration of runtime data to accomodate for incompatible changes. This should fix #30.
Yet To Do: