Upload Version Checklist

Complete these steps whenever a new version of a managed or unmanaged package is uploaded for distribution. 

 

Release Plan

StatusTO DO

Sprint

 

JIRA Issue

 
Versions 

Uploaded By

 
Help Doc By 

Validated By

 
Released By 

Cartoon of an assemble-it-yourself job interview for Ikea furniture.

 

 Topic (tick)

(minus)

(warning)

Remark
1Release DashboardCreate Release Dashboard issue to track version deployment.
  •  
  •  
  •  
 
2Seasonal WorkspaceAnnounce short-term plan on seasonal workspace blog for product and target release type (seasonal, milestone, emergency).
  •  
  •  
  •  
 
3Build ServerReview build server for any build issues, and resolve pertinent errors before continuing. 
  •  
  •  
  •  
 
4 When development tasks are complete, move issue to Uploading column.
  •  
  •  
  •  
 
5Git BranchesCreate transient copy of develop branch and PR from transient branch to target release branch.
  •  
  •  
  •  
 
6fixVersionEnsure that all development issues in the pull request are tagged for the fixVersion.
  •  
  •  
  •  
 
7Release DatesUpdate issue tracker, landing and change logs with final version number. Set the issue tracker fixVersion Start Date to today. 
  •  
  •  
  •  
 
8Epic BranchesMerge transient develop into epic branches (if needed).
  •  
  •  
  •  
 
9Git MergingMerge pull request into target release branch.
  •  
  •  
  •  
 
10Extension PackagesFor extension packages, install any updated dependency to target packaging org.
  •  
  •  
  •  
 
11Deploying Salesforce Code

Deploy to target packaging org via build server.

  •  
  •  
  •  
 
12Compile All Classes

When deployment succeeds, Compile All Classes in packaging org.

  •  
  •  
  •  
 
13 Execute Apex tests in packaging org. 
  •  
  •  
  •  
 
14Package Manifest

If package.xml is not up to date, add new components by hand.

(Use build log as guideline.)

  •  
  •  
  •  
 
15Managed ComponentsAdd list of added components to Change Log, and comment on blog.
  •  
  •  
  •  
 
16Package Upload

Pending feedback on added components, upload the major or patch release.

(warning) When upload form loads, confirm that unexpected new dependencies are not added.

  •  
  •  
  •  
 
17Branch TaggingTag the release branch in Git.
  •  
  •  
  •  
 
18Version IDWhen the upload completes, update the packaging org's LastPass Notes to include the new "candidate" Version ID.
  •  
  •  
  •  
 
19Firewall SandboxInstall the new version in the firewall sandbox. 
  •  
  •  
  •  
 
20Install ScriptsConfirm that "install script failure" or other unexpected alerts are not present. 
  •  
  •  
  •  
 
21API Regression TestsRun the global regression test suite.
  •  
  •  
  •  
 
22Mock Customer TSOInstall version into the Mock Customer Trialforce Source Org (TSO).
  •  
  •  
  •  
 
23Version TSOInstall the new version into the Version TSO.
  •  
  •  
  •  
 
24TSO TemplatesProvision a new template in each TSO (even if other versions are pending).
  •  
  •  
  •  
 
25Development OrgsFor the Preview channel, update the settings for the Trialforce Request Form and ChatOps.
  •  
  •  
  •  
 
26

Help Topics

Move Release Dashboard issue to the Documenting column, and assign to technical writer.
  •  
  •  
  •  
 
27Patch OrgProvision patch org; deprecate older versions if needed.
  •  
  •  
  •  
 
28Patch BranchCreate a patch branch from the package/*.org branch (package/*_#.#.patch)
  •  
  •  
  •  
 

(tick) Yes - (minus) No - (warning) Not Applicable