This technology is considered preview.
The above quote is from https://quarkus.io/guides/amazon-lambda
This is the blocker to consider the extension for the production usage.
What is the ETA for reaching the "stable" status?
Thanks, Alex
Related
It's been three weeks since I applied for the release of the app from the Google Play Console.
It is still under review.
This time it's just a minor display improvement, but why is it taking so long?
I've heard that the coronavirus is having an impact, but this time it's too late, and I can't release the iOS app, which has already been reviewed, at the same time.
Is there something wrong with Google right now?
Am I the only one taking this long? How is everyone else doing?
By default, your app will use standard publishing. Certain apps may be subject to extended reviews, which may result in review times of up to 7 days or longer in exceptional cases.
I suggest to talk with chat support to speed up the review process, since you already exceeded the 7 day review period, they will review it manually and publish it
can someone tell me how can I setup webspeed on progress 4gl 60 days trial version for a practice purpose? I tried so much but found no way to set up in trial version. Any online environment anything in which I can practice?
Thanks in advance for your help and support guys...
The current release of Progress, and thus the downloadable trial, is OpenEdge 12. WebSpeed was retired in OpenEdge 11 and is, therefore, not available in the OpenEdge 12 trial.
We are going to run Cobalt on our device, and consider to the stability for partners' development.
We'd like to know...
The official version that Cobalt recommends.
Would Cobalt have a regular official version released? If the answer is yes, may I know the period of the release?
It would be great to know this information for partners preparing the environment for the future development.
Thank you.
The master branch at https://cobalt.googlesource.com/cobalt/+/master/ will always stay close to the internal development trunk. It will be a moving target in terms of stability, but will also see features first.
Release branches are sequentially named, COBALT_2, COBALT_3, and so on. They are named on when they branch, not when they stabilize, but in general it will be safest to port and release off of the latest stable release branch. These branches have gone through testing and released on one or more real production platforms.
Since this is still early days, there isn't a regular release schedule yet, but it is being worked towards. There will be more details on that when plans are finalized.
So far they're the only people I can find that are doing a chart control...
What happens when the beta expires? How does it expire? (Does it expire?). They look great but there is no pricing information or expiry information.
Here is a direct quote from the EULA:
“You may distribute the Programs as embedded in Your Integrated Products to Your end-users only pursuant to an end-user license that meets the requirements of this Section.”
So, yes, you can ship Apps built with Telerik Windows 8 Controls Beta to the Store.
"Beta," by definition, suggests not ready for production use.
There are at least a couple of things you should think about before moving forward:
Does the license agreement for the controls allow use in a production app (you did read the license, right?)
Are you willing to risk the possibility that the app might suddenly stop working for any and all users who have downloaded it, until such time as you replace the controls with working versions (and get the updated version of your app submitted to the store)?
As long as the controls fit the Windows 8 app design, and don't cause performance or crashing issues, they may not have any impact on whether or not the app gets through certification.
But the larger issue is one of risk. Betas are for testing. IMO, unless the beta includes a "go-live" license, you should probably stick with using beta software for evaluation and testing only.
To be clear, that's no knock on Telerik's beta quality (or anyone else's, for that matter). Just a reminder that beta software isn't finished yet.
In a FDA regulated environment applications need to be validated. I've done that tons of times in my career but now I'm facing SAAS. Has anyone out there faced this before? Any FDA related guideline on this scheme?
Besides some black box approach and much support from the provider I see this as hard to do.
I hear ya!
It is impossible...
check out: http://www.vantagesystems.com/Library/Pharmaceutical%20Commerce_Article_%20IMPROVING%20ERP%20IN%20THE%20LIFE%20SCIENCES%20INDUSTRY.pdf
Since original link is dead, here's a wayback machine archive link for the same article
https://web.archive.org/web/20100601233736/http://www.vantagesystems.com/Library/Pharmaceutical%20Commerce_Article_%20IMPROVING%20ERP%20IN%20THE%20LIFE%20SCIENCES%20INDUSTRY.pdf
It is indeed possible to run a validated SaaS for medical devices.
In fact here is QPharma's perspective on this.
Note I am not affiliated with QPharma, but I am very much interested in SaaS and validation techniques. The point is it is indeed quite possible!