Ch-ch-ch-ch-changes ... Turn and face the STRANGE

Ch-ch-ch-ch-changes ... Turn and face the strange



Here is my unsolicited expert advice:

(1) Create an ongoing option for a user to either (1) opt in to a new release or (2) rollback to a prior release

(2) In addition to whatever development testing is done by QuickBse staff, test new releases with an early access program. I am sure there are hundreds of customers who would love to evaluate a new release of QuickBase and provide immediate feedback.

(3) Develop a list of user focused policies such as:

   "new features should not disturb existing implementations"
   "new features should not change the appearance or behavior of forms or reports without user approval"
   ...