This commit is contained in:
@@ -1,9 +1,8 @@
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 6 - "MAKE IT HAPPEN" All in on porting over all the real objects from v7
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 6 - BETA "MAKE IT HAPPEN" All in on porting over all the real objects from v7
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
“Accept the things to which fate binds you, and love the people with whom fate brings you together,but do so with all your heart.”
|
||||
― Marcus Aurelius, Meditations
|
||||
|
||||
"Make it happen"
|
||||
- Jim July 28th 2021
|
||||
|
||||
@@ -24,9 +23,7 @@ Prioritize anything that stands in the way of beta testing
|
||||
|
||||
|
||||
|
||||
TODO: NEXT:
|
||||
Testing section below #1 cases
|
||||
|
||||
TODO:
|
||||
|
||||
Update all dependencies
|
||||
Server section below for the AGE interval bug then can go back to regularly scheduled items
|
||||
@@ -36,17 +33,16 @@ Update all dependencies
|
||||
also needs to see if it's affecting any intervals used anywhere else in ayanova like can you select months in a contract/pm/notification etc?
|
||||
Weeks is the highest safe time frame interval that can be used with this but I'm almost certain there are months in there somewhere
|
||||
|
||||
|
||||
|
||||
the testing cases and triage the stuff below added recently with an eye to what is needed for beta specfically adn what is needed for initial release and what should be bumped to v.next (make into case)
|
||||
report sample stuff limited to report designer roles and etc
|
||||
|
||||
reporting issues
|
||||
testing cases
|
||||
#1 issues below in list
|
||||
docs cleanup
|
||||
features in immediate block below
|
||||
|
||||
|
||||
# OUTSTANDING MAJOR AREAS TO BETA
|
||||
|
||||
- Features
|
||||
|
||||
TEST MODE
|
||||
comment out or put in a debug block all
|
||||
internal static bool AYANOVA_SERVER_TEST_MODE { get; set; }
|
||||
@@ -57,6 +53,7 @@ the testing cases and triage the stuff below added recently with an eye to what
|
||||
For beta I don't think this is particularly critical, users will likely jump straight to migration anyway no matter what we tell them to do
|
||||
docs
|
||||
see docs section below for beta docs issues
|
||||
Important to go through all existing docs and cleanup re-read every single page and put under construction if not ready yet
|
||||
dashboard widgets
|
||||
Not the highest priority for BETA but there shoudl be at least a couple so that feature can be tested also it shoudl at least replicate v7 stuff
|
||||
Just enough an no more, this could be endless, come up with a top 5 or something and limit it to that
|
||||
@@ -159,17 +156,20 @@ Coded by importance
|
||||
╚═╝╚═╝ ╚═══╝╚══════╝ ╚═╝ ╚═╝ ╚═╝╚══════╝╚══════╝
|
||||
|
||||
|
||||
- 1 todo: test single liner upgrade command in linux:
|
||||
sudo systemctl stop ayanova.service && rm *.dll && rm -r ./resource && rm -r ./wwwroot && unzip -o ayanova-linux-x64-server.zip -x "config.json" && sudo systemctl start ayanova.service
|
||||
|
||||
- 1 todo: update the version of postgreSQL in the "single" standalone installer (but do it for myself first in my dev standalone pg server)
|
||||
|
||||
- 1 todo: apparently it's easy to pick an alternate folder for install in windows single and it fucks with postgres path so not sure what to do with that
|
||||
- 1 todo (may be done already I think?): apparently it's easy to pick an alternate folder for install in windows single and it fucks with postgres path so not sure what to do with that
|
||||
maybe force the default installation location for windows single only so people don't fuck it up?
|
||||
Or add a warning we *STRONGLY advise not changing the default location or you will need to change config.json
|
||||
or, is it possible to write out the config.json from the installer and not include it as a physical file??
|
||||
This way it can properly write out whatever paths necessary in single installer at least
|
||||
|
||||
|
||||
|
||||
|
||||
- 2 todo: test single liner upgrade command in linux:
|
||||
sudo systemctl stop ayanova.service && rm *.dll && rm -r ./resource && rm -r ./wwwroot && unzip -o ayanova-linux-x64-server.zip -x "config.json" && sudo systemctl start ayanova.service
|
||||
|
||||
- 2 todo: subscribe to all sources of security vulnerabilities that could apply to users of AyaNOva 8 (and 7)
|
||||
Need an ongoing defined process to follow to ensure we are not caught by surprise with any security vulnerabilities
|
||||
Github watch and star all tools used for starters so get notifications via github about new releases etc
|
||||
@@ -188,8 +188,8 @@ Coded by importance
|
||||
╚═════╝ ╚═════╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝╚══════╝╚═╝ ╚═══╝ ╚═╝ ╚═╝ ╚═╝ ╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═══╝
|
||||
|
||||
TODO: 1 BETA DOCS:
|
||||
- installation docs
|
||||
- OPS docs, lots of important and missing stuff particularly backup and restore
|
||||
- *** IMPORTANT *** before beta go through *every* doc page one at a time and read through them for outdated stuff and wording that should not be public
|
||||
|
||||
- administration setup which should be mostly done but go over it and find missing bits that a beta tester will need
|
||||
- MIGRATION docs, there *must* be a migration page and it needs to tie into the installation docs perhaps
|
||||
- evaluation docs where it explains about trial license and requesting and generating data etc, just the basic process and why to do it that way
|
||||
@@ -213,8 +213,6 @@ TODO: 1 BETA DOCS:
|
||||
CLEANUP, go through each docs page look for swear words, inside info, stuff that shouldn't be there and replace with UNDER CONSTRUCTION instead
|
||||
|
||||
|
||||
-2 Mirror docs to our site so we can link to a central place for them when doing website and for beta test, installation etc
|
||||
|
||||
-1 Somewhere document that a login is good for 5 days from moment of login before needing to login again
|
||||
|
||||
|
||||
@@ -229,7 +227,7 @@ TODO: 1 BETA DOCS:
|
||||
|
||||
- 1: change the installer to be named v8-migrate.exe and publish it to the new download/ folder instead
|
||||
also update the version number to match the release, since it likely won't change much maybe just make it 8.0.0-beta.1 directly
|
||||
|
||||
|
||||
|
||||
## TESTING ITEMS
|
||||
████████╗███████╗███████╗████████╗██╗███╗ ██╗ ██████╗
|
||||
@@ -240,20 +238,7 @@ TODO: 1 BETA DOCS:
|
||||
╚═╝ ╚══════╝╚══════╝ ╚═╝ ╚═╝╚═╝ ╚═══╝ ╚═════╝
|
||||
|
||||
|
||||
|
||||
- 1: todo: run a load test, document how to and then record baseline on devops server for standard load test
|
||||
|
||||
here can get back to restore and age bug fixes etc for b7
|
||||
|
||||
|
||||
|
||||
- 3 todo: Keep eye on this, it seems it went away mostly when I stopped accidentally regenerating data on every test but for now will consider it a non-issue
|
||||
deploy to linux server test heavily and see if this error crops up again or is it just my pc:
|
||||
Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Unexpected end of request content
|
||||
could it be a non async route? https://tipsfordev.com/unhandled-exception-in-asp-net-core-web-api-on-linux
|
||||
|
||||
|
||||
-1 todo: check out this SPA memory leak detector, it *does* have a login ability btw in case it's not obvious, something about extras or ...?
|
||||
-2 todo: check out this SPA memory leak detector, it *does* have a login ability btw in case it's not obvious, something about extras or ...?
|
||||
https://github.com/nolanlawson/fuite
|
||||
|
||||
|
||||
@@ -290,7 +275,6 @@ here can get back to restore and age bug fixes etc for b7
|
||||
\_____|______|_____|______|_| \_| |_|
|
||||
|
||||
|
||||
- 1 todo: signature image control in main wo form now has border and gray color, stands out, looks weird, sb hidden maybe if no sig or...?
|
||||
|
||||
- 1 todo: Unlicensed doesn't allow any troubleshooting info, make sure that the user can still get to ops when unlicensed and view server configuration or whatever
|
||||
is required to troubleshoot failed install
|
||||
@@ -304,11 +288,12 @@ here can get back to restore and age bug fixes etc for b7
|
||||
- 1 translation cleanup, work order sb Orden de trabajo but is translated as Pedido?! (which is very generic and not work order, usually like a restaurant order or online shipping order sense for pedido)
|
||||
I did a couple but realized it needs to be done one by one roundtripped carefully as it's used in alternative tenses and forms throughout
|
||||
|
||||
|
||||
|
||||
|
||||
-2 Schedule, what is the maximum number of techs can show in team view, can show more with scroll?
|
||||
seeder should prevent going over this max (tags/prefilter/gen less)
|
||||
|
||||
|
||||
|
||||
- 2 metrics ops page should show the little dots so know where to position the mouse to see the reading at that point
|
||||
also, there needs to be more "dots", it's too few to get proper idea
|
||||
also todo under server that metrics isn't really capturing the whole server metrics only the ayanova process metrics as far as I can tell
|
||||
@@ -328,7 +313,6 @@ todo:2 PO (workorder already done) strip all *viz fields from object before send
|
||||
Setting their value to undefined stops them being sent so do that, but remember they then need to be updated on the return record
|
||||
PO I'm thinking is the main one??
|
||||
|
||||
|
||||
todo:2 Not in love with the "Error api2200" as the only error text in the box
|
||||
sometimes it has things you can't see in the form
|
||||
ideally I'd like to see it have a string of text as a duplicate showing the errors translated in a list
|
||||
@@ -350,7 +334,6 @@ todo:2 reporting custom fields
|
||||
Maybe translated custom fields alongside the string version??
|
||||
Users see it as currency would be just as confused as Joyce was expecting it to be a number
|
||||
|
||||
|
||||
todo: 2? schedule form sync with ical, there's a case for it
|
||||
|
||||
todo:3 link back to list from single edit form
|
||||
@@ -463,27 +446,7 @@ todo: 3 Schedule form reporting?
|
||||
|
||||
|
||||
|
||||
todo: 1 VERY IMPORTANT test on windows where all paths have spaces, i.e. set the server data path to a location with funky folder names with spaces etc
|
||||
confirm everything in raven that writes to disk still works, logging, backup, attachments, temp files served (reports) etc
|
||||
|
||||
TODO: 1 Log the startup folder for AyaNova and provide in all areas where you can view config because user may have trouble locating it on windows
|
||||
|
||||
todo: 2 lost contact with db server notification message to be sent once to ops admin??
|
||||
don't want too many but should notify
|
||||
|
||||
todo: 1 When there is a rendering issue with chromium browser startup the server *must* log that to the server log, right now it just half-ass reports it back to the client only
|
||||
this is because it was written expecting any error was a template error not a starting chromium error so need to look there in the exception handler
|
||||
would rather not log report template issues to the server log but anything else structural should be
|
||||
|
||||
todo: 2 Test with expired key, can superuser login and no one else?? **CRITICAL**
|
||||
Awaiting a raven license key generator first, currently do not have one, 404's in rockfish!!
|
||||
todo: 2 rockfish generate keys for purchased licenses, the real deal
|
||||
|
||||
todo: 1 investigate: noticed when rebooting linux server I need to login again which I didn't expect, it should still work as long as the token is unchanged
|
||||
is this due to randomization of jwt secret or something?
|
||||
try in windows and confirm
|
||||
|
||||
todo: MAJOR ISSUE FOR US can't use inteval / timespan the way we have
|
||||
todo: 1 MAJOR ISSUE FOR US can't use inteval / timespan the way we have
|
||||
was a pending issue preventing upgrade to npgsql 6.0.1 from 6.0.0
|
||||
https://github.com/npgsql/efcore.pg/issues/2157
|
||||
Update: this is a serious change due to interval handling
|
||||
@@ -491,14 +454,28 @@ todo: MAJOR ISSUE FOR US can't use inteval / timespan the way we have
|
||||
timespan stuff like notifications and contracts etc etc because they don't do epochs greater than weeks?
|
||||
Maybe it's just the age query itself that is affected.
|
||||
|
||||
todo: 1 VERY IMPORTANT test on windows where all paths have spaces, i.e. set the server data path to a location with funky folder names with spaces etc
|
||||
confirm everything in raven that writes to disk still works, logging, backup, attachments, temp files served (reports) etc
|
||||
|
||||
TODO: 1 Log the startup folder for AyaNova and provide in all areas where you can view config because user may have trouble locating it on windows
|
||||
|
||||
todo: 1 When there is a rendering issue with chromium browser startup the server *must* log that to the server log, right now it just half-ass reports it back to the client only
|
||||
this is because it was written expecting any error was a template error not a starting chromium error so need to look there in the exception handler
|
||||
would rather not log report template issues to the server log but anything else structural should be
|
||||
|
||||
|
||||
todo: 2 Test with expired key, can superuser login and no one else?? **CRITICAL**
|
||||
Awaiting a raven license key generator first, currently do not have one, 404's in rockfish!!
|
||||
todo: 2 rockfish generate keys for purchased licenses, the real deal
|
||||
todo: 2 lost contact with db server notification message to be sent once to ops admin??
|
||||
don't want too many but should notify
|
||||
|
||||
todo:2 Joyce case 3931 test restore of 4alarm data
|
||||
Get a copy from Joyce on the red drive, it's about 5gb
|
||||
write up how to do it if there are manual steps (there will be I guess but maybe there shouldn't be)
|
||||
make sure it works one way or another
|
||||
confirm it's really backing up everything
|
||||
|
||||
|
||||
|
||||
todo: 2 make priority / woitem / wostatus colors distinct from each other
|
||||
whitecaps color scheme shale/pastel etc
|
||||
Note: wostatus will be the default color source so concentrate on making that look nice and clean
|
||||
@@ -812,13 +789,15 @@ MID CENTURY MODERN TUNES - https://www.allmusic.com/album/ultra-lounge-vol-14-bo
|
||||
|
||||
https://www.ayanova.com/download/v8/ayanova-windows-x64-single-setup.exe
|
||||
https://www.ayanova.com/download/v8/v8-migrate.exe
|
||||
|
||||
Current v8 docs home: https://www.ayanova.com/docs/
|
||||
|
||||
BUILD 8.0.0-beta.0.6 CHANGES OF NOTE
|
||||
|
||||
- fixed bug in history that would bomb if a taskgroup name needed to be displayed
|
||||
- many minor changes to support e2e testing
|
||||
- new *permanent* download urls case 4053 for details
|
||||
- new docs folder hosting current version of v8 docs https://www.ayanova.com/docs/
|
||||
this is for our use so don't need to spin up a server to view the docs but will likely be the permanent url for v8 docs once all is done
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user