Hi,

 

before performing a major version upgrade I’d like to test and learn / experiment with new versions. I would like to step in directly when a new beta is started, like the beta series for version 7. 
 

the problem however is i would either need to boy a license or request a 30 day trail ket. The beta program runs much longer than 30 days which disqualifies this option. 
 

it would be great if the beta versions would not require a lisence key but have some other form of protection for misuse (as production environment). Perhaps put a fixed enddate and/or a max uptime of a couple of days. Maybe there are other options to consider. 

for me this would be great because it would help me test new versions before i actually upgrade my production environment without having to buy a license.

 

regards Richard
 

 

 

On 10/13/2024 at 3:47 AM, Richard Aarnink said:

Perhaps put a fixed enddate and/or a max uptime of a couple of days.

 

The first option might be workable if there's a new beta available before the previous one times out, but I'd still argue that's a bad solution because it would prevent A/B testing. The second option is out of the question and would impact people's ability to test/report, not to mention just run the OS.

 

I've been running 7.00 betas since they first came out on every one of my production machines and I'd hate to have anything change that would prevent that in the future.

 

So maybe there needs to be a special optional BETA testing key type that has these limits such that it won't impact anyone using their standard keys with the beta releases.

 

 

Edited October 18, 20241 yr by Espressomatic