Digital Product Release - Readiness Target Date vs Change "Schedule"

[Tommaso2]

Hi all,

It is no clear to me which is the relationship between Readiness Target Date in DPR and Change request "Schedule" phase.

Indeed in the print below it seems that CR comes later, so I expect the "Schedule" dates to be "when" the change will be actually released and the Readiness Target Date I assume is the date before which all tasks and validations have to be completed (but then I open the CR and I schedule the effective release date).

Nevertheless, I found the comment below in Now Learning where it seems that Readiness Target Date happens later than "CR are approved":

So how these two dates are related? Can you please provide an example?

Many thanks

[Siva Sankar Ala · Accepted solution]

@Tommaso2 
Release readiness date is the date where all the planned phases tasks are supposed to be completed and ready for deployment.
Right now we have no strict validations or connections between change request schedule and release readiness date because change requests could be of different types.
For example after development phase is complete if we wanted the "Dev" Server needs to be updated with the latest artifact we might create a change request for DEV server. In this case Release readiness date could be after the change schedule.
Let's say if your change request is to deploy the artifacts into production your Change request schedule date can be after the release readiness phase.

[Siva Sankar Ala · Accepted solution]

@Tommaso2 
Release readiness date is the date where all the planned phases tasks are supposed to be completed and ready for deployment.
Right now we have no strict validations or connections between change request schedule and release readiness date because change requests could be of different types.
For example after development phase is complete if we wanted the "Dev" Server needs to be updated with the latest artifact we might create a change request for DEV server. In this case Release readiness date could be after the change schedule.
Let's say if your change request is to deploy the artifacts into production your Change request schedule date can be after the release readiness phase.

[onedapaone · Accepted solution]

@Siva Sankar Ala  

We can let one main change request be tagged as the Release CR and have this validation performed that this should come on or after Release target date.

Also, Environment field on Change Request can be leveraged to find out which is Production environment CR.

Having this check will help not to have CR scheduled before release target date.