Project

General

Profile

Actions

User story #18557

closed

Adapt rudder package to support new versionning scheme

User story #18557: Adapt rudder package to support new versionning scheme

Added by Vincent MEMBRÉ about 5 years ago. Updated over 4 years ago.

Status:
Released
Priority:
N/A
Category:
Plugins integration
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
To do
Fix check:
To do
Regression:

Description

We want to change plugin versionning so that we can release plugins with every new release of Rudder on the following versioning X.Y.Z-a.b instead of X.Y-A.b where Z is the patch release of the plugin. This will allow us to ensure that the plugins are compatible with each release of Rudder


Subtasks 1 (0 open1 closed)

User story #19145: parent ticket broke the rudder-pkg testsReleasedVincent MEMBRÉActions

Related issues 1 (0 open1 closed)

Related to Rudder - Architecture #18886: rudder package should base its version on rudder-relay package rather rudder agent version outputRejectedActions

Updated by Vincent MEMBRÉ about 5 years ago Actions #1

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ

Updated by Vincent MEMBRÉ about 5 years ago Actions #2

  • Assignee changed from Vincent MEMBRÉ to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder/pull/3358

Updated by Vincent MEMBRÉ about 5 years ago Actions #3

  • Target version changed from 6.2.0~rc1 to 7.0.0~beta1

Updated by Vincent MEMBRÉ almost 5 years ago Actions #4

  • Related to Architecture #18886: rudder package should base its version on rudder-relay package rather rudder agent version output added

Updated by Vincent MEMBRÉ almost 5 years ago Actions #5

  • Status changed from In progress to Pending release

Updated by Vincent MEMBRÉ over 4 years ago Actions #6

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 7.0.0~beta1 which was released today.

Actions

Also available in: PDF Atom