publish

Publishing a Release Note

The triggers for Release Note publication for General, Update, and Hot Fix releases are described in the overall Release Note Process.

To publish an online Release Note for a new release:

1. Receive approval from the team (particularly, Development Manager and QA Manager) on the technical content of the Release Note page for the 7-digit release, Welcome page for the Component Release Note, and Known Issues page for the component.
2. Receive a peer-edit and apply any copy-editing corrections to the pages.
3. Receive a format approval from Pubs Editors.
4. Make sure you are logged in to the Documentation wiki.
5. On the DRAFT Release Note page for the 7-digit release, select the publish release note tab.
6. On the Genesys Release Note Generator page that appears, confirm the publication of the 7-digit Release Note page. Click Publish Draft.
7. The Genesys Release Note Generator: Publish Draft—Complete page appears. Here, right-click and Open in New Tab/Window the following links:
   1. The Release Note for the 7-digit release. On the page that opens, verify that the content was moved from the DRAFT version to the final RN Manual. Click Edit and Save the page.
   2. The Welcome page for the Component’s Release Note. On the page that opens, verify that the content was moved from the DRAFT version to the final RN Manual, including the link to the new 7-digit release. Click Edit and Save the page.
8. If you made any manual changes to the TOC in the Draft version, they don’t carry over. Repeat the required TOC updates in the published version. For example, add or remove 3-digit release pages for 8.5.1, 8.5.2, etc. releases, if required.
9. To publish Known Issues, go to the DRAFT Known Issues page and select the publish known issues tab.
   Note: Yes, the Known Issues page has to be explicitly published because publication of the 7-digit release page does not include Known Issues. This separation enables you to update Known Issues independently of a release.
10. On the Genesys Release Note Generator page that appears, confirm the publication of the Known Issues page. Click Publish.
11. The Genesys Release Note Generator: Publish Known Issues—Complete page appears. Here, right-click and Open in New Tab/Window the Known Issues link. On the page that opens, verify that the content was moved from the DRAFT to the final version. Click Edit and Save the page.

Note: If you receive an error during the publication process, check whether the RN was published despite the error. To do so, navigate to the final version of your 7-digit release page by replacing the DRAFT version number with the final number (such as, 8.5.x) in the URL. If the page does not exist, contact the Pubs RN Admin alias to publish your RN manually.

Your wiki Release Note has been published.

After publishing the online, wiki Release Note, do the following:

• Publish the Release Note freeze form in XING, unless the RN is associated with v9.0 (formerly G-NINE) and has been decoupled from the IP.
• Verify that the Release Notes link from your product landing page on the Documentation site points to the Welcome page of the Component’s Release Note.

Updating a Previously Published Release Note

If you need to make any changes to a previously published Release Note, including an additional operating system or updated release type, always make the change in the DRAFT version of the Release Note first. Then follow the same process as for Publishing a Release Note.

Publishing/Updating Known Issues

If you need to make any changes to a previously published Known Issues page (including an additional issue, updated description, or Found In/Fixed In version), always make the change in the DRAFT version of the Known Issues page first. Then follow steps 8 through 10 of the process for Publishing a Release Note.