...
- Samuel Valdez (Unlicensed)
SF PROD WEB - Samuel Valdez (Unlicensed)
DR PROD WEB - Samuel Valdez (Unlicensed)
SF PROD DB - Samuel Valdez (Unlicensed)
SF PROD AUTO
24 - On the day of the release, re-send the announcements that were sent in Steps 13 and 14, for the last time, and preferably in the morning.
...
25 - A few minutes after the scheduled start of the release, send an announcement that the release is about to begin. The email should be addressed to DT-EAS-User-Group and CC-ed to DT-SFGIS-User-Group. An example of this email was sent on 1/18/2019 3:05 PM, and can be found in Outlook's Sent Items, or Deleted Items, folders.
26 - Follow the instructions that are in the release's draft version deployment details page that was created in Step 7 above, and edit them as needed.
...
27 - Send an announcement, that is analogous to the one that was sent in Step 13 above, that heralds the successful release. The email should be addressed to DT-EAS-User-Group, and CC-ed to DT-SFGIS-User-Group and DT-EAS-New-Release-Announcement. This is related to issue #234. An example of this email was sent on 1/18/2019 6:02 PM, and can be found in Outlook's Sent Items, or Deleted Items, folders.
- Samuel Valdez (Unlicensed) Email
- Samuel Valdez (Unlicensed) Yammer
28 - Complete the change request that was created in Step 9 above.
29 - Update the Bitbucket issue that was created in Step 3 above by setting the version of the issue to the version of this release, for example "1.3.8", and then close the issue. Do not forget to find the comment in the issue that should be pinned to the top, and then pin it.
29A - Close every issue that was resolved in every milestone that is part of this release.
...