User story #5628
closed
User story #5610: Add a "deprecated" attribute and notice for Technique version
Manage Deprecated properties from technique metadata
Added by Vincent MEMBRÉ about 10 years ago.
Updated over 9 years ago.
Category:
Web - Config management
Description
Add a new section in metadata.xml that contains information about deprecation.
the xml section section would look like that
<DEPRECATED>
<VERSION>In which version of Rudder that technique has been deprecated (mandatory)</VERSION>
<MESSAGE>A specifc message (optionnal)</MESSAGE>
</DEPRECATED>
- Pull Request set to https://github.com/Normation/cf-clerk/pull/56
- Status changed from New to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Priority changed from N/A to 2
I'm wondering if "since" in place of version isn't clearer ?
For example:
<DEPRECATED since="2.11">Here the message</DEPRECATED>
- Status changed from Pending technical review to 10
- Assignee changed from François ARMAND to Jonathan CLARKE
- Status changed from 10 to Pending technical review
- Assignee changed from Jonathan CLARKE to Nicolas CHARLES
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset clerk:commit:6f3c8a21601eb38bb177d53215baaaa3de3f14e0.
Applied in changeset clerk:commit:265a45ade4e1a98708efff6fdc083a7a85afa204.
- Target version changed from 140 to 3.0.0~beta1
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta1 which was release on 01/12/2014.
- Category changed from 14 to Web - Config management
- Tracker changed from Enhancement to User story
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Matthieu CERDA 
Updated by