User story #9025
open
rudder-dev should not deprecate old versions of techniques
Added by Jonathan CLARKE over 8 years ago.
Updated about 8 years ago.
Category:
Rudder dev tools
Description
According to https://github.com/Normation/rudder-techniques/pull/1015/, rudder-dev can create a new version of a technique, but marks the previous one deprecated immediately.
This is not reasonable behaviour: if we provide a technique version in Rudder major version X.Y, we cannot deprecate that same version in a patch version of X.Y. It is expected that anything in a major version is maintained and supported and upgradable for the lifetime of that version. We can only deprecate it in X.Y+1.
I guess rudder-dev code needs changing to reflect this.
You're right.
Can we say that the deprecate behavior is valid in master and that in other branhc we never deprecate automatically a technique ?
Benoît PECCATTE wrote:
You're right.
Can we say that the deprecate behavior is valid in master and that in other branhc we never deprecate automatically a technique ?
Yes, that sounds good to me.
Although maybe we'd want to deprecate all versions in master automatically?
What do you mean by automatically ? outside of rudder-dev ?
And what do you mean by all versions ?
I mean apply the same logic you originally implemented, but on the master branch.
That is, if I'm creating a new technique version 3.1 from 3.0, we probably want to deprecate 3.0 in master. Right?
This behavior would be very hard to do when creating a new technique version in an old branch, since the deprecation has to be in a separate PR.
Benoît PECCATTE wrote:
This behavior would be very hard to do when creating a new technique version in an old branch, since the deprecation has to be in a separate PR.
Sure, so keep it for later. The main point here is as described in the subject.
- Tracker changed from Bug to User story
Also available in: Atom
PDF
Updated by 
Updated by Jonathan CLARKE