Difference between revisions of "Publish a Package"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
Line 14: | Line 14: | ||
#::: After publication, it is displayed in as version in the Package object | #::: After publication, it is displayed in as version in the Package object | ||
#::* The Package object stored version numbers and notes for the last five (5) versions. | #::* The Package object stored version numbers and notes for the last five (5) versions. | ||
#:;Version Notes:Notes about the package | #:;Version Notes:Notes about the package. <br>These notes appear in the revision list for the package. |
Revision as of 22:58, 25 July 2011
Publishing a package makes it available for tenants to install. It also makes it possible for the publisher (you) to automatically upgrade local Package Subscribers, using the Deploy option.
To publish a Package:
- Follow the instructions to Create a Package, then Add items to the Package.
- Click [Publish] to begin the process, or click [Edit] to make changes to the package before publishing
- Provide the following information:
- Name
- Name of the package
- Version
- Version number of the package.
- The default value is an auto-incrementing dot-version.
- If the Package version is "1", the default will be "1.1". If the Package version is "1.1", the default will be "1.2". Etc.
- The value can be changed to whatever you like.
- After publication, it is displayed in as version in the Package object
- The Package object stored version numbers and notes for the last five (5) versions.
- Version Notes
- Notes about the package.
These notes appear in the revision list for the package.