Actions
User story #8934
closedRename Rudder 3.3 to 4.0
Status:
Released
Priority:
N/A
Assignee:
Category:
Architecture - Code maintenance
Target version:
Effort required:
Name check:
Fix check:
Regression:
Description
We are bumping Rudder version to 4.0 in master because:
- next major will be 4.0, not 3.3 (major changes, among them Policy Mode: Verify, + bunch of incompatibles changes in packaging, initial promise management, etc)
- if we need to release a Rudder 3.3 for some reason before 4.0, it is impossible to fork it from master, due to the previously depicted changes
- we don't want to wait the last minute to have build and doc with 4.0 everywhere.
This ticket just handle the version bump in Rudder pom. Other tickets will be open as children to change other parts of Rudder.
Updated by Alexis Mousset about 8 years ago
- Tracker changed from Bug to User story
Updated by Alexis Mousset about 8 years ago
- Status changed from New to In progress
Updated by Alexis Mousset about 8 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1185
Updated by Alexis Mousset about 8 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|716de057dcfbdf8b53f719d9ec5302646638849f.
Updated by Benoît PECCATTE about 8 years ago
- Target version changed from 4.0.0~rc2 to 318
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 318 to 4.0.0~rc2
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 4.0.0~rc2 to 4.0.0~rc1
Updated by Alexis Mousset about 8 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.0 which was released the 10th November 2016.
Actions