Lets read that again and let it soak in "Why you should NEVER use pre-release builds, that contain bug fixes in my view."
They require ongoing (possibly indefinite) subscriptions even if patched during your current subscription", to be clear lets read the text at the top of the Patch Download Page - I've seen it hundreds of times - but didn't really read it through.
The devil is in the last line. Here it is again.
I'll break it down - what it is saying is something like this - if you purchased your AA licence say on September 30, 2015 - and it will expire on September 29 2016, last build you are entitled to use is the LAST OFFICIAL RELEASE of AA ( Or Official Patch) in this case the last Official Release build is build is 3670_4684 (released on 13 JUN 2016 09:33 AM) as stated above - and not the pre-release build (that contains bug fixes) you were on at the time.
This means the definition of subscription is based on the cycle of whatever Official Release you may encounter during your subscription period. It means the subscription is provided 'as is' and does not necessarily include bug any fixes for past issues that will work in the future should you not subscribe beyond the current subscription, in this case, the clients sub that expired on September 29 2016, will no longer have access to bug fixes provided since 13 JUN 2016 09:33 AM, as the client needs to return back to that build, even though his code contains the bug fix material provided, this is clearly disastrous as the code will no longer work.
The problem comes about mainly because bug fixes are mixed up with new pre_release builds, that is you can't have one without the other - the questions then is - if this is so - then what is the subscription for? What are you getting along the way during the period you didnt have at the start!
This is an issue of catastrophic proportions - the idea business access pre-release updates to fix issues that clearly needing fixing - will have non-functioning applications later - In this case October 1st unless they subscribe again to the same 13 JUN 2016 09:33 AM build in the hope at some time in the future a new Official Release is made available during the new subscription period.
I really don't know what to think about all this - but what I do know, is at the very least the Bug fixes released during the subscription period must remain available after the subscription expires.
In the 12 months Prior 13 JUN 2016 09:33 AM there were 11 Official Release Updates - since 13 JUN 2016 09:33 AM there have been none.
They require ongoing (possibly indefinite) subscriptions even if patched during your current subscription", to be clear lets read the text at the top of the Patch Download Page - I've seen it hundreds of times - but didn't really read it through.
Alpha Anywhere Updates
The current Alpha Anywhere (Alpha Five Version 12) build is 3670_4684 (released on 13 JUN 2016 09:33 AM).
Please note that Alpha Anywhere patches are only available to users with a current subscription. You can verify your subscription status from within Alpha Anywhere by going to Help, About, or by clicking this link.
If you install an update for which your subscription is not entitled, you will need to uninstall the update and rollback to an older version that you are authorized to use in order to continue using Alpha Anywhere.
The current Alpha Anywhere (Alpha Five Version 12) build is 3670_4684 (released on 13 JUN 2016 09:33 AM).
Please note that Alpha Anywhere patches are only available to users with a current subscription. You can verify your subscription status from within Alpha Anywhere by going to Help, About, or by clicking this link.
If you install an update for which your subscription is not entitled, you will need to uninstall the update and rollback to an older version that you are authorized to use in order to continue using Alpha Anywhere.
If you install an update for which your subscription is not entitled, you will need to uninstall the update and rollback to an older version that you are authorized to use in order to continue using Alpha Anywhere.
This means the definition of subscription is based on the cycle of whatever Official Release you may encounter during your subscription period. It means the subscription is provided 'as is' and does not necessarily include bug any fixes for past issues that will work in the future should you not subscribe beyond the current subscription, in this case, the clients sub that expired on September 29 2016, will no longer have access to bug fixes provided since 13 JUN 2016 09:33 AM, as the client needs to return back to that build, even though his code contains the bug fix material provided, this is clearly disastrous as the code will no longer work.
The problem comes about mainly because bug fixes are mixed up with new pre_release builds, that is you can't have one without the other - the questions then is - if this is so - then what is the subscription for? What are you getting along the way during the period you didnt have at the start!
This is an issue of catastrophic proportions - the idea business access pre-release updates to fix issues that clearly needing fixing - will have non-functioning applications later - In this case October 1st unless they subscribe again to the same 13 JUN 2016 09:33 AM build in the hope at some time in the future a new Official Release is made available during the new subscription period.
I really don't know what to think about all this - but what I do know, is at the very least the Bug fixes released during the subscription period must remain available after the subscription expires.
In the 12 months Prior 13 JUN 2016 09:33 AM there were 11 Official Release Updates - since 13 JUN 2016 09:33 AM there have been none.
Comment