8.0.3 release

devdocs/deploy.md

@@ -6,7 +6,7 @@ If any packages have been changed in the release do a thorough security scan and
 
 ### Bump version numbers:
 
-Search and replace 8.0.2  
+Search and replace 8.0.3  
 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,

devdocs/pricing.md

@@ -139,7 +139,7 @@ TWO types makes the most sense after considering options:
 -   One time fee, user can use indefinitely
 -   self installed, hosted and maintained by customer
 -   least profitable for us long term if they don't buy a maint. subscription
--   Without maintenance subscription, eligable for Minor updates only to fix bugs no new features so in other words they buy 8.0.2 they can upgrade to any 8.0.X version release, but not 8.1 as it will be new features added that don't break backward compatibility
+-   Without maintenance subscription, eligable for Minor updates only to fix bugs no new features so in other words they buy 8.0.3 they can upgrade to any 8.0.X version release, but not 8.1 as it will be new features added that don't break backward compatibility
 -   one-time payment, along with the option of a yearly maintenance fee.
 -   This is basically our current model but we allow upgrades for subscribers
 -   **HAS CODE IMPLICATIONS** upgrades need to check if allowed based on version number if no maintenance subscription _not_ on date of build.

devdocs/todo.txt

@@ -8,9 +8,17 @@ without hassle
 
 RESEARCH: sendgrid / email system can we have a domain just for our notifications for those that don't use their own domain and use for all users (but NOT tied to AyaNova.com)
 https://linuxhandbook.com/set-up-discourse-digital-ocean/ has an example of discourse with Mailgun freen email ssytem and a domain
+(NOT MAILCHIMP AFTER HACK that affected digitalocean they sound like dicks)
 
 TEST: cheapest storage for attachments possible, test out creating a new droplet with block storage to hold the attachment files to see if it's possible, how it's done and mapped etc
 
+
+todo: implement and test now system to prevent download subscription instance database and just use locally, i.e. check for special file or whatever system we implement
+	 check for subscription key file presence and signature inside to be checked in case they parse the code and put teh file by that name needs to be not enough but signed inside too
+
+todo: can user use erase key flag to get trial and then use trial for 5 days and just keep on doing that or isn't there a check to erase db first??
+	needs some way to ensure this doesn't happen, maybe a user check or something or some sign it's not eval??
+
 todo: maintenance plan agreement?  SB something in the license docs I guess since it differs, also license text will need to be chagned as it is on assumption of built in maint before
 	Here is autodesks maintenance plan agreement page: https://www.autodesk.com/company/legal-notices-trademarks/autodesk-terms-and-conditions/eng_autodeskmaintenancesubscriptiontermsandconditions
 
@@ -25,7 +33,7 @@ todo: on ops server info page show main disk usage of db, attachments free memor
 
 todo: v8migrate Contracts in v7 were allowed to have no name, add code to invent a name on migration so it doesn't bomb
 
-todo: QBI don't check build date against expiry date if it's a trial, i.e. they can upgrade a trial all they want as long as it's not expired key
+todo: license agreement changes for perpetual, since maint is no longer included or maybe just add 30 day bit and bit about optional maintenance agreement and keep in one place
 
 todo: License agreement changes for SAAS customers, this is huge and I hadn't thought of it before, wording is very different in this case, fuck, need to wing it I guess
 	https://flgpartners.com/saas-pivots-transitions-perpetual-to-subscription-saas-models/
@@ -39,9 +47,12 @@ todo: SAAS gaming, once have idea of plans and add-ons, need to test it out on s
 todo: ROCKFISH different license key signature if it's a SAAS license
 	this solves a lot of problems, effectively it's unlicensed if they move their data to their own hardware without a key
 	requires that AyaNova have different internal key to check, maybe it's actually a build switch for that since only we will be running our SAAS version.
+	dual signatures doesnt' work becuase it would mean ayanova could just work anyway since it can check either, need something else.
+	build switch would work but it means a whole separate build every tiem which is fucky, but maybe necessary.
 
 todo: ROCKFISH can't make a trial key for users in the UI, only when it's requested from ayanova.
 	I'm really not sure if this is an issue or not but putting it on the list in case
+	add as a feature just in case
 
 todo: DOCS - remove all mention of digitalocean from the install and other docs since we're going to be using them for SAAS we don't want to make it simple for people to host themselves, just say Linux and leave it at that.
 
@@ -1237,10 +1248,6 @@ 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.2 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
-Fixed potential lockout situation in AyaNova front end with force change known password code
-Expanded roles allowed to fetch license to support integration of external applications
+BUILD 8.0.3 CHANGES OF NOTE
 
+Allow negative quantities on most work order subitems