Prepare Your Apps for Distribution
- Enter a Version Name. As a bestpractice, it's useful to have a short description and the date.
- Enter a Version Number for theupload, such as 1.0. The format is majorNumber.minorNumber.NoteIf you’re uploading a new patch version, you can't change the patch number.The version number represents a release of a package. This field is required for managed and unmanaged packages. For a managed package, the version number corresponds toa Managed - Released upload. All beta uploads use the same version number untilyou upload a Managed - Released package version with a new version number. For example, the following is a sequence of version numbers for a series of uploads.Upload SequenceTypeVersion NumberNotesFirst uploadManaged - Beta1.0The first Managed - Beta upload.Second uploadManaged - Released1.0A Managed - Released upload. The version number does not change. Third uploadManaged - Released1.1Note the change of minor release number for this Managed - Releasedupload.Fourth uploadManaged - Beta2.0The first Managed - Beta upload for version number 2.0. Note the majorversion number update.Fifth uploadManaged - Released2.0A Managed - Released upload. The version number does notchange.
- For managed packages, select a Release Type:Choose Managed - Released to upload an upgradeable version. After upload, some attributes of Salesforce components are locked. Choose Managed - Beta if you want to upload a version of your package to a small sampling of your audience for testing purposes. You can still change the components and upload other beta versions. Note Beta packages can only be installed inDeveloper Edition or sandbox organizations, and thus can't be pushed to customerorganizations.
- Choose Managed - Released to upload an upgradeable version. After upload, some attributes of Salesforce components are locked.
- Choose Managed - Beta if you want to upload a version of your package to a small sampling of your audience for testing purposes. You can still change the components and upload other beta versions. Note Beta packages can only be installed inDeveloper Edition or sandbox organizations, and thus can't be pushed to customerorganizations.
- Change the Description, ifnecessary.
- Optionally, specify a link to release notes for thepackage. Click URL and enter the details in the text field thatappears. This link will be displayed during the installation process, and on the PackageDetails page after installation.Note As a best practice, point to an external URL, so you can make the information available to customers before the release, and update it independently of the package.
- Optionally, specify a link to post installinstructions for the package. Click URL or Visualforce page and enter the details in the text field that appears. This link willbe displayed on the Package Details page after installation. Note As a best practice, point to an external URL, so you can update the information independently of the package.
- Optionally, enter and confirm a password to share thepackage privately with anyone who has the password. Don't enter a password if you wantto make the package available to anyone on AppExchange and share your packagepublicly.
- Salesforce automatically selects the requirements itfinds. In addition, select any other required components from the Package Requirements and Object Requirements sections tonotify installers of any requirements for this package.
- Click Upload.
