Page History
...
- Bugs, vulnerabilities and patches are communicated with our the SOS Change Management System.
- Patches are provided per release. The corresponding fixes are integrated with the next maintenance release or with the next minor release.
- For vulnerabilities in of 3rd-party components the Change Management System indicates where to the download location of the patch and how to apply the patch.
- For severe bugs in JS7 components SOS provides patches that are available for download from the issue description.
- Find below the information how to apply patches for the respective JS7 components.
Change Management System
The public SOS Change Management System keeps track of any changes including patches and bug-fixes:
- For example, consider a 3rd-party vulnerability such as
Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1229 - The issue description provides immediate instructions how to replace patch 3rd-party libraries.
- Users download patched libraries from the 3rd-party vendor's site.
- The issue is reported for release 2.2.1 that can be patched from the instructions. Subsequent releases 2.2.2 and later include the updated libraries to fix the issue. The patch therefore must not be applied to releases 2.2.2 or later.
- For example, consider a bug such as
Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1235 - The issue is reported to affect release 2.2.2 and us is fixed with release 2.2.3.
- For immediate resolution a patch file is offered for download. This patch can be applied to the indicated release 2.2.2, it cannot be applied to earlier releases and it must not be applied to later releases.
Resources
Display children header |
---|
...
Overview
Content Tools