Patches:

Patches:

Patch versions are developed and maintained in a patch development organization. For more information on push upgrades and patches, see the Force.com Quick Reference for Developing Packages. You can also read the Best Practices for Push Upgrades and Patch Versions.

To create a patch version:

1. Click Your Name | Setup | Create | Packages.
2. Click the name of your managed package.
3. Click the Patch Organization tab and then click New.
4. Select the package version that you want to create a patch for in the Patching Major Release drop-down list. The release type must be Managed - Released.
5. Enter a Username for a login to your patch organization.
6. Enter an Email Address associated with your login.
7. Click Save.
8. After you receive an email indicating Salesforce has created your patch development organization, you can click Login to begin developing your patch version.
9. Development in a patch development organization is restricted. The following is a list of caveats:

   • New package components can’t be added.
   • Existing package components can’t be deleted.
   • API and dynamic Apex access controls can’t change for the package.
   • No deprecation of any Apex code.
   • No new Apex class relationships, such as extends, can be added.
   • No new Apex access modifiers, such as virtual or global, can be added.
   • No new Web services can be added.
   • No new feature dependencies can be added.
   When you finish developing your patch, in your patch development organization:

   1. Click Your Name | Setup | Create | Packages and click the name of the package.
   2. On the Upload Package page, click Upload.
   3. Enter a Version Name. As a best practice, it's useful to have a short description and the date.
   4. Notice that the Version Number has had its patchNumber incremented.
   5. For managed packages, select a Release Type:
      • Choose Managed - Released to upload an upgradeable version. After upload, some attributes of Salesforce components are locked. For a list of locked attributes, see Developing Packages for Distribution.
      • Choose Managed - Beta if you want to upload a version of your package to a small sampling of your audience for testing purposes. You'll still be able to change the components and upload additional beta versions. For information on beta versions, see Developing Packages for Distribution.
        1. Change the Description, if necessary.
        2. Optionally, enter and confirm a password to share the package privately with anyone who has the password. Don't enter a password if you want to make the package available to anyone on AppExchange and share your package publicly.
        3. Salesforce automatically selects the requirements it finds. In addition, select any other required components from thePackage Requirements and Object Requirements sections to notify installers of any requirements for this package.
        4. Click Upload.
        To distribute your patch, you can either share the upload link, or schedule a push upgrade.