|
See
Also
Before you create a patch for
a release, the release must have been exported.
To define and create a patch
for a release:
| 1.
|
From the Repository Manager menu, select Define, Releases. |
The Releases window
opens.
| 2.
|
Perform a query that retrieves the release for which you want
to create a patch. |
|
ALTERNATIVE:
|
You can also open the release from the catalog, by
double-clicking on the name.
|
| 3.
|
Check that this release has been exported. |
The Released field contains the date and
time of this release.
| 4.
|
In the bottom part of the window, define a Patch Nr. |
This can be any number or
code, up to 8 characters long. As a suggestion, you could use any
of the following codes:
3, alpha, security, 20100530.
| 5.
|
Define a Target
Repository. |
Almost always, this will be
the Repository Code of the
release.
| 6.
|
Optionally, set the USoft Import XML field to Yes if you want
to generate an Import XML document that can be used to apply the
patch to a repository that is identical to the release. |
These manipulations can then
be executed in the Definer of a repository that is exactly
identical to the release.
|
IMPORTANT:
|
Executing these manipulations is at your own risk.
|
| 7.
|
Optionally, set the PDF Report field to Yes if you want to
generate a difference report in PDF format. |
The patch is now listed on
the Manage tab of the
catalog, under the release.
| 9.
|
Click the Create Patch button. |
An export is made of the
target repository. Then, the patch (comparison) is created, and the
Created field is set to
the current date and time.
| 10.
|
You can click the View
Patch button to view the patch in an external editor. |
|
