Once we have developed, documented and Tested an EASAP, we need to Publish it for a User to access.
An EASAP will evolve and improve based on new requirements or user feedback.
EASA provides the capability to publish a Minor or a Major new release of an EASAP.
This paragraph will describe how EASA deals with new and old versions of an EASAP.
First of all, EASA automatically archives old versions of EASAPs when new releases are published to the Application Library. Therefore, results from runs made by users with older versions of an EASAP automatically retain an association with the older version that was used to generate them.
To access the appropriate older version of an EASAP, all users need to do is click on the Open button () in the EASAP column of their My Results table. Therefore, as an author, you should not need to republish old versions of EASAPs when users want to continue making runs with an older version that they have already used.
As an author, you do have control over the link between EASAP runs stored in the Results Library and the EASAP version used to make the runs. You can delete old versions using the Publish History page found under the Authoring menu in Author mode. To delete an old version of an EASAP, click on the Delete button () in the Delete column and then click on the Delete button to confirm. More information on the use of the History page is provided in the following section.
Another reason old EASAP versions are maintained by EASA is to allow authors to revert back to them if new versions do not work out as well as planned. You access old EASAP versions by selecting Publish History under the Authoring menu. This selection will display a table of all version of an EASAP that have been published throughout its history. To revert to a previous version, you complete the following steps:
The other capability provided on the Publish History page is the deletion of old EASAP versions, which is accomplished by clicking on the Delete button () and then on the Delete button to confirm.
As you develop and publish several versions of an EASAP, you should also continue to develop the help files for this EASAP. Details on the creation of help files and suggestions for their content are provided at the Document an EASAP page.
A ‘Release Notes’ section near the beginning / top of an EASAP’s help files could prove helpful as versions beyond 1.0 are published for an EASAP. This section might include the following information: