Build Notification Process n n n The email

Build Notification Process n n n The email “Build Notification” is sent by a Manager to “System QA” mailing list The notification must be sent by 8: 30 am every Monday morning The message says “there is a build available” ¨ ¨ ¨ n OR The message says “there is no build available and here is the reason” ¨ ¨ ¨ n Build identifiers (time stamp, directory name, that uniquely identifies build) An exact location (and provide any password information required) Any additional items needed to successfully install (installation instructions) The Build failed The BAT failed Something else (be specific) QA Manager compiles status Monday morning and reports to all noon. ¨ ¨ Which products? See The Release Components. xls spreadsheet Do not send old builds (if your current build fails)

Standard Build Process n n Tuesday/Wednesday ¨ Infrastructure and libraries Build ¨ Component Team starts BAT ¨ Send notification when build is done Thursday ¨ All other products build ¨ Send notification when builds identified Friday through Sunday ¨ QA teams run BAT ¨ Send notification when BAT complete. ¨ Saturday and Sunday are slack days. They can be used to get the build working, if there are problems. Monday 8: 30 am ¨ Teams send build notifications ¨ System QA Accepts builds ¨ Weekly “Test Cycle” begins ¨ Infrastructure and libraries test cycle is ahead of all other teams by two days.