...
19 - Formally qualify the release candidate in the EAS QA environment per the instructions that are here a day or two before the release. Store the test results in the (artifact) directory that is specified in the Bitbucket issue that was created in Step 3.
- Dan King (Unlicensed) User Interface
- Samuel Valdez (Unlicensed) Unit Testing
- Samuel Valdez (Unlicensed) Change Notification Emails
...
If the release candidate was not successfully qualified, then proceed to Section 5 below, Cancel the Release.
...
- Find the comment in the issue that should be pinned to the top, and then pin it.
- Update the value of the "Actual: " milestone that is in the issue's description, for example, with "2019-02-12-A".
- Update the version of the issue to the version of this release, for example "1.3.8".
- Update the milestone of the issue to "---------" (none).
21A - Visit every issue that was not resolved in every milestone that is part of this release, and perform the following tasks. This is the first step in rolling these issues into a future milestone:
- Insert the value of the "Target: " under the last targeted milestone that is in the issue's description.
- Update the milestone of the issue to "high", "medium", or "low". The most likely choice is "high".
22 - Update the Sprints and Product Releases table for all of the milestones that are in this release with the new information (see the lists of table columns below), ideally on the day before, or of, the release.
- Actual SV, Actual DK, Actual Total
- Difference SV, Difference DK, Difference Total
23 - During the morning of the release, the person who will perform the release, and their backup, should verify their VPN connectivity to all of the relevant machines.
- 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.
- Samuel Valdez (Unlicensed) Email
- Samuel Valdez (Unlicensed) Yammer
...
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.
...