beta .2 doc changes
This commit is contained in:
@@ -9,7 +9,7 @@ If any packages have been changed in the release do a thorough security scan and
|
||||
|
||||
### Bump version numbers:
|
||||
|
||||
Search and replace 8.0.0-beta.1
|
||||
Search and replace 8.0.0-beta.2
|
||||
webapp,server,launcher, v8migrate
|
||||
|
||||
Client end ayanova-version.js,
|
||||
|
||||
@@ -1,21 +1,34 @@
|
||||
# now
|
||||
Update docs, stress hosting onine in v7 chyanges
|
||||
make build beta.2 and post, make post in forum indicating change
|
||||
give Joyce the go-ahead to email people
|
||||
get back to docs completion
|
||||
start in on QBI
|
||||
rockfish front end improvements, revocation, license link that does nothing??
|
||||
product codes or feature options to include??
|
||||
what exactly is rental in the license doing?
|
||||
is license versioned for format?
|
||||
|
||||
|
||||
keepass proper way to use and how to split for security etc?
|
||||
trialing plan for setting up server, do we charge? how much, what questions do we need answered to set up droplet
|
||||
More beta testers, open it up to public beta
|
||||
update forum first, remove in development text change to in beta and give a post with beta info where to get the manual and download etc
|
||||
email to chunks of selected users daily / need to get going on this
|
||||
stress can be hosted online rather than using in-house somehow, so email should have a top line sentence or two blurb of why they might be interested in it etc.
|
||||
|
||||
|
||||
Figure out how we can offer it for testing online?
|
||||
hosted instances spun up on a single server devops (beefed up)
|
||||
round robin time limited licensed keys??
|
||||
prevent migration?
|
||||
|
||||
|
||||
Key name and passphrase to unlock it
|
||||
C:\data\work stuff\digitalocean\keys\v8trialprivatekey.ppk
|
||||
ANY TRIAL SERVER@helloayanova.com: workingatthecarwash
|
||||
|
||||
|
||||
# OUTSTANDING BEFORE RELEASE
|
||||
|
||||
#1 items below in each category, some #2 as well
|
||||
|
||||
todo: test with licensed key to ensure evaluate is gone and everything works logging in as each user to regular home page
|
||||
todo: test key revocation
|
||||
|
||||
critical path items:
|
||||
- docs completed
|
||||
@@ -26,24 +39,16 @@ critical path items:
|
||||
- License agreement change from beta to regular
|
||||
- Docs completed filling in, many empty pages still
|
||||
- business stuff like rockfish, licensing new site, new forums (update docs links when new forum), direct purchase
|
||||
- Beta testing completed
|
||||
|
||||
|
||||
|
||||
|
||||
- Beta testing completed
|
||||
this is going to be huge because users will find a million bugs and issues with how things work and it will be a big clusterfuck for a while so plan for time and patience
|
||||
|
||||
|
||||
- Here switch from BETA to RC designation, let it soak for a bit before full release
|
||||
- onboarding process for v7 users guide to migration and also including licensing and etc which requires figuring out pricing and shit
|
||||
trial / seeder system
|
||||
do not specify by size but rather scenario
|
||||
we care about size for load testing but don't want to give impression we think HUGE is just a few 10s of thousands of workorders because it's a db issue at a certain point
|
||||
Also NO time estimates in the UI, just make sure they are all a reasonable length of time to generate, like no more than 15 minutes or something, ideally less than 5 minutes
|
||||
|
||||
This should be coded by *task* rather than object to make life easier when we implement
|
||||
i.e. a MakeWorkorderItemPartRequest task would go through the rigamarole of making a part request, a PO to fulfil it etc
|
||||
or something along those lines, ideas fuzzy at the moment
|
||||
maybe it's what is there plus additional Task based ones
|
||||
maybe the UI drives it because we have specific ideas for that
|
||||
|
||||
- Plugin / addon replacements implemented and fully tested
|
||||
qbi - 4alarm can't migrate until this is done
|
||||
@@ -94,7 +99,17 @@ todo: ARCHIVE ALL DEPENDENCIES
|
||||
|
||||
|
||||
|
||||
- THIS CAN WAIT TIL AFTER RELEASE IT"S NOT HOLDING UP EXISTING USERS BUYING
|
||||
trial / seeder system
|
||||
do not specify by size but rather scenario
|
||||
we care about size for load testing but don't want to give impression we think HUGE is just a few 10s of thousands of workorders because it's a db issue at a certain point
|
||||
Also NO time estimates in the UI, just make sure they are all a reasonable length of time to generate, like no more than 15 minutes or something, ideally less than 5 minutes
|
||||
|
||||
This should be coded by *task* rather than object to make life easier when we implement
|
||||
i.e. a MakeWorkorderItemPartRequest task would go through the rigamarole of making a part request, a PO to fulfil it etc
|
||||
or something along those lines, ideas fuzzy at the moment
|
||||
maybe it's what is there plus additional Task based ones
|
||||
maybe the UI drives it because we have specific ideas for that
|
||||
|
||||
|
||||
|
||||
@@ -801,5 +816,5 @@ https://www.ayanova.com/download/ayanova-linux-x64-server.zip
|
||||
https://www.ayanova.com/download/ayanova-windows-x64-lan-setup.exe
|
||||
Current v8 docs home: https://www.ayanova.com/docs/
|
||||
|
||||
BUILD 8.0.0-beta.1 CHANGES OF NOTE
|
||||
BUILD 8.0.0-beta.2 CHANGES OF NOTE
|
||||
|
||||
|
||||
Reference in New Issue
Block a user