In Recast AW I can create a scheduled task to download and apply updates for packages I added from the setup store.
I can also set the stage.
Our goal is to apply updates automatically as quick as possible when the impact is low. For example an update for 7-zip can be done without any testing.
But when it comes to Visual C++ or Java, the impact can be very high.
I believe we can now only set the default phase on the setup store which is the same for all packages.
We would like to be able to set the default phase per package. This way we can make sure an update (for example 7-zip) to go directly to the production phase when it comes available in the setup store, and for example for java we can automatically set it to the Acceptance phase.
For full automation it would also be great that we can set an acceptance period.
Being able to set the acceptance period generally in Recast AW.
In the package we will be able to enable or disable the use of the acceptance period
In the package we set the default phase to acceptance
The scheduled task puts a newly available update to the acceptance phase based on the package settings
After the acceptance period has past, the update automatically gets from acceptance to production.
As an extra comment we see the demands from for example BIO2 and NIS and from the customers that we need to be able to patch as soon as possible. But because of impact we need to have more control over which package we can and which package we need to be able to test first. But doing this manually for all our customers is impossible.