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

Final release candidate 8.0.1 - holy shit commit!

Browse Source
This commit is contained in:
John Cardinal
2022-08-05 23:55:49 +00:00
parent d95510cf48
commit ad61269560
8 changed files with 31 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
devdocs/deploy.md
View File

@@ -6,14 +6,14 @@ If any packages have been changed in the release do a thorough security scan and
### Bump version numbers:
Search and replace 8.0.0
webapp,server,launcher, v8migrate
Search and replace 8.0.1
webapp,server,launcher, v8migrate (don't change v8migrate unless it has it's own code changes, it's version should be it's own thing other than major release changes etc)
Client end ayanova-version.js,
Server end ayanova-version.cs
The TWO windows installers are versioned
Server end ayanova-version.cs AND AyaNova.csproj
The TWO windows installers are versioned (LAN.ISS and STANDALONE.ISS)
RavenLauncher "single" Launcher is also versioned and needs to be changed individually
Docs index.md file is also versioned
Docs are not versioned but dated in mkdocs.yml copyright property so if that needs to change be sure it's udpated
#MyAppVersion in C:\data\code\raven\dist\install\windows\x64\lan.iss
#MyAppVersion in C:\data\code\raven\dist\install\windows\x64\standalone.iss

17
devdocs/todo.txt
View File

@@ -7,17 +7,6 @@ LICENSE STUFF
Updates:
Test that can't upgrade to newer release if support and updates not current!!!!
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
@@ -28,8 +17,8 @@ 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
*** todo: test on every platform every installer and be certain they work as advertised, yes this is a pain but it's necessary
Once all platforms pass all tests then and only then move to regular download folder and post about it on forum post
@@ -1148,7 +1137,7 @@ https://www.ayanova.com/download/next/ayanova-linux-x64-server.zip
https://www.ayanova.com/download/next/ayanova-windows-x64-lan-setup.exe
Current v8 docs home: https://www.ayanova.com/docs/next
BUILD 8.0.0 rc2 CHANGES OF NOTE
BUILD 8.0.1 rc2 CHANGES OF NOTE
Added integration back end feature for integration of external applications with AyaNova 8
Added front end administrative UI for viewing and controlling integrated applications and their logs