PoolParty Versioning
Starting with PoolParty 2022 Release 1, the PoolParty components are versioned independently, following the conventions of semantic versioning (for example 9.0.2). The platform version (for example PoolParty 2022 Release 2) serves as an overarching version of the PoolParty Semantic Suite.
Release Date | Thesaurus Server | Extractor | GraphSearch | Recommender | Workbench | UnifiedViews | PoolParty for SharePoint | Application Development Framework |
|---|---|---|---|---|---|---|---|---|
Jul. 2024 | 9.3.2 | 9.3.2 | 9.3.2 | 1.0.2 | 2.0.0 | 10.0.0 | 9.3.0 | 1.3.0 |
Jun. 2024 | 9.3.0-9.3.1 | 9.3.0-9.3.1 | 9.3.0-9.3.1 | 1.0.2 | 2.0.0 | 10.0.0 | 9.3.0 | 1.3.0 |
Release Date | Thesaurus Server | Extractor | GraphSearch | Recommender | Workbench | UnifiedViews | PoolParty for SharePoint | Application Development Framework |
|---|---|---|---|---|---|---|---|---|
Mar./Apr. 2024 | 9.2.1–9.2.3 | 9.2.1–9.2.3 | 9.2.1–9.2.3 | 1.0.1 | 1.1.0 | 9.0.5 | 9.2.0 | 1.2.0 |
Jan. 2024 | 9.2.0 | 9.2.0 | 9.2.0 | 1.0.1 | 1.0.1 | 9.0.5 | 9.1.0 | 1.1.0 |
Release Date | Thesaurus Server | Extractor | GraphSearch | Recommender | Workbench | UnifiedViews | PoolParty for SharePoint | Application Development Framework |
|---|---|---|---|---|---|---|---|---|
Dec. 2023 | 9.1.1 | 9.1.1 | 9.1.1 | 1.0.1 | 1.0.1 | 9.0.4 | 9.1.0 | 1.1 |
Sept. 2023 | 9.1.0 | 9.1.0 | 9.1.0 | 1.0.0 | 1.0.1 | 9.0.3 | 9.0.1 | 1.0 |
Release Date | Thesaurus Server | Extractor | GraphSearch | UnifiedViews | PoolParty for SharePoint |
|---|---|---|---|---|---|
19/10/2023 | 9.0.7 | 9.0.7 | 9.0.7 | 9.0.2 | 9.0.1 |
23/08/2023 | 9.0.6 | 9.0.6 | 9.0.6 | 9.0.2 | 9.0.1 |
16/05/2023 | 9.0.2 | 9.0.2 | 9.0.2 | 9.0.2 | 9.0.1 |
12/05/2023 | 9.0.2 | 9.0.2 | 9.0.2 | 9.0.2 | 9.0.0 |
23/03/2023 | 9.0.1 | 9.0.1 | 9.0.1 | 9.0.1 | 9.0.0 |
01/12/2022 | 9.0.0 | 9.0.0 | 9.0.0 | 9.0.0 | 9.0.0 |
PoolParty's Semantic Versioning
PoolParty's Semantic Versioning
PoolParty Semantic Suite uses semantic versioning and provides major, minor and patch versions. Semantic versioning is a formal convention for specifying compatibility using a three-part version number: major version, minor version, and patch. The patch number is incremented for minor changes and bug fixes that do not change the software application programming interface (API). The minor version is incremented for releases that add new, but backward-compatible API features, and the major version is incremented for API changes which are not backward-compatible. For example, software which relies on version 2.1.5 of an API is compatible with version 2.2.3, but not necessarily with 3.2.4.
PoolParty API Compatibility:
Major versions can break the API compatibility.
Minor versions can change the API, but always keep backward compatibility.
Patch versions do not change the API.