Project

General

Profile

Actions

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.

Status:
Released
Priority:
1 (highest)
Category:
Web - Config management
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

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>


Subtasks 1 (0 open1 closed)

Bug #5652: updte test of cf-clerk to handle deprecationInfoReleasedNicolas CHARLES2014-10-16Actions
Actions #1

Updated by Vincent MEMBRÉ about 10 years ago

  • Pull Request set to https://github.com/Normation/cf-clerk/pull/56
Actions #2

Updated by Vincent MEMBRÉ about 10 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Priority changed from N/A to 2
Actions #3

Updated by François ARMAND about 10 years ago

I'm wondering if "since" in place of version isn't clearer ?

For example:

<DEPRECATED since="2.11">Here the message</DEPRECATED>
Actions #4

Updated by François ARMAND about 10 years ago

  • Status changed from Pending technical review to 10
  • Assignee changed from François ARMAND to Jonathan CLARKE
Actions #5

Updated by Vincent MEMBRÉ about 10 years ago

  • Status changed from 10 to Pending technical review
  • Assignee changed from Jonathan CLARKE to Nicolas CHARLES

We finally removed the version tag too hard to use correctly ( which version should be put in ? ) and force the usage of a text in the deprecated tag to use as message

PR here: https://github.com/Normation/cf-clerk/pull/56

Actions #6

Updated by Vincent MEMBRÉ about 10 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset clerk:commit:6f3c8a21601eb38bb177d53215baaaa3de3f14e0.

Actions #7

Updated by Nicolas CHARLES about 10 years ago

Applied in changeset clerk:commit:265a45ade4e1a98708efff6fdc083a7a85afa204.

Actions #8

Updated by Matthieu CERDA about 10 years ago

  • Target version changed from 140 to 3.0.0~beta1
Actions #9

Updated by Vincent MEMBRÉ about 10 years ago

  • 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.

Actions #10

Updated by Benoît PECCATTE almost 10 years ago

  • Category changed from 14 to Web - Config management
Actions #11

Updated by Benoît PECCATTE over 9 years ago

  • Tracker changed from Enhancement to User story
Actions

Also available in: Atom PDF