Actions
Bug #12331
closedrudder-pkg must disable plugin during major version Rudder update
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
Plugins are linked to Rudder major version API, and so they won't work after a major upgrade, even perhaps breaking things in a subtile way. So during a major version upgrade, we should disable all plugins, warn the user, and let the user install new versions (in one go once #12330 is done).
Updated by François ARMAND over 6 years ago
- Translation missing: en.field_tag_list set to Blocking 4.3
I'm setting that one as "blocking 4.3" even if it targets 4.2 because we must have it around the time that we release 4.3.
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.11 to 4.1.12
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.12 to 4.1.13
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 4.1.13 to 411
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 411 to 4.1.13
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.13 to 4.1.14
Updated by François ARMAND over 6 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND over 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder-packages/pull/1610
Updated by François ARMAND over 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|59842c969704680c8f880c1a727faf113e3391e7.
Updated by François ARMAND over 6 years ago
- Target version changed from 4.1.14 to 4.1.13
Updated by Vincent MEMBRÉ over 6 years ago
- Status changed from Pending release to Released
Actions