Actions
User story #8462
closed
Document the server/agent compatibility matrix
Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Documentation
Target version:
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
Compatibility matrix¶
| agent\server | 2.10 | 2.11 | 3.0 | 3.1 | 3.2 |
| 2.10 | x | x | x | ||
| 2.11 | x | x | x | x | x |
| 3.0 | x | x | x | x | x |
| 3.1 | x (unsupported) | x | x | x | x |
| 3.2 | x (>= 3.1.11) | x |
The constraints are:
- Migration script: starting from 3.1, only 2.11+ migrations are supported / explicit classic protocol breaks 2.10
- 3.2+ agent need explicit protocol classic, only present in 3.1.11+
Upgrade paths¶
| from\to | 2.10 | 2.11 | 3.0 | 3.1 | 3.2 |
| 2.10 | x | x | |||
| 2.11 | x | x | (x) | ||
| 3.0 | x | x | |||
| 3.1 | x | ||||
| 3.2 |
- x: direct upgrade possible
- (x): direct upgrade possible, but servers have to be upgraded before agents
Updated by Alexis Mousset over 8 years ago
- Related to User story #8459: Document precisely compatibility between servers and nodes in 3.2 doc added
Updated by Benoît PECCATTE almost 8 years ago
- Is duplicate of User story #8479: Add compatible agent versions to release-data added
Actions