Releases

You can manage the life cycle of a partition by creating a release each time you need to distribute a new version of the rendered partition content.

A partition release is a document snapshot defined when a partition is first created and then each time you create a new update. A looseleaf partition will include at least two releases — an update phase and a published phase. The update phase contains material being prepared for the next release. The published phase contains the material most recently published.

When you compose a partition, TopLeaf creates one or more output pages using the content referenced from the partition update phase. In a typical update cycle, both the input content and the stylesheets used to produce the rendered output may be adjusted until an approved set of output pages is produced.

TopLeaf assumes that the page output is not acceptable unless the input content is rendered without composition errors or warnings. To enforce this rule, all publishing controls are disabled until a partition is typeset without error. The partition properties include an option to allow publishing a change pages release if there are warnings but not errors.

When all changes to the partition content are complete, and the rendered output is correct, the partition update is ready to be published. TopLeaf creates a new document baseline using the current update phase, and this becomes the new published phase of the partition. If you have decided to track changes between releases, TopLeaf uses the published release as a baseline to detect changes made during the next update cycle.

The ability to manage releases is an important part of looseleaf publishing.