admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

maintenance expiration vs build date checking code

Browse Source
This commit is contained in:
John Cardinal
2022-08-05 23:31:37 +00:00
parent 379ba76b31
commit d95510cf48
8 changed files with 96 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
devdocs/todo.txt
View File

@@ -12,7 +12,12 @@ Updates:
it should also have some license route fetch prevention i.e. license has updates end date so server won't send if expired? Or something along those lines??
Or maybe that would be bad if they downgrade and want to put back in the license they paid for (restore from backup?)
Update scenarios to handle
boot with newer version than licensed and no db at all
in this case it's ok to do the schema update and install the fresh empty db then fetch the license
LICENSE FETCH SHOULD COMPARE DATES BEFORE INSTALLING A FETCHED LICENSE AND BALK IF MISMATCH
Boot with newer version and have existing db with outdated schema
TODO: it should check the license version *before* the schema update in order to not break anything
todo: RELEASE FINAL RELEASE
@@ -23,7 +28,7 @@ todo: RELEASE FINAL RELEASE
test carefully once done reversion everything to 8.0.1 for official release
Post in /next download folder for testing before posting fully
Re-run the smoke tests and e2e tests before posting 8.0.1 officially
todo: test on every platform every installer and be certain they work as advertised, yes this is a pain but it's necessary