2013-05-10 Release

Submit change request

Open a build/test change request in https://yale.service-now.com/, assign to INF SN App Support

minutes

Schedule code review

this should happen after initial handover and before release

minutes

Build

Begin work in dev

days

Developer tests

Ensure all pushed to and unit tested in test

hours

Push to Test

Hand over initial requirements list for functional & QA validation

minutes

Testing

UAT & product testing (testing instance)

days

(missed)

Conduct code review

Shouldn't take long, just basic validation of approach and docs

hours

Defect fixes

Iterative follow-up work in dev, test for defect resolution

days

Code Freeze

Identify changes & updates that have passed both testing regimes. Push to preproduction.

hours

(in progress)

Regression Testing

QA group conducts regression testing in preproduction

minutes

()

Go/no-go

Decide to push to production.

minutes

()

Production deployment

Push to prd.

hours

()

Production rollback

If applicable; follow ServiceNow Rollback Procedure.

hours

()

Clone

clone from prd to: pre, trn, and tst for after release

hours

()

Push to Test

re-push outstanding, ready work back to test

hours

()

Notify stakeholders

send out email w/ summary status & link to release documentation, close out RFC and cancel clone requests, if rollback or no-go.

minutes

2013/04/29 - 5

FRU0014333 - Requirement 786 - Request: New Catalog Item: "WordPress Feature Request"

• fix help text, regex for site url

2013/04/29 - 4

FRU0014332 - Requirement 791 - Request: New Catalog Item "WordPress Site Request"

• fix to regex

2013/04/26 - 2

FRU0014332 - Requirement 791 - Request: New Catalog Item "WordPress Site Request"

2013/04/23 - 1

FRU0014333 - Requirement 786 - Request: New Catalog Item: "WordPress Feature Request"