TINP deprecation: Difference between revisions
Jump to navigation
Jump to search
m (moved TINP replacement to TINP deprecation) |
No edit summary |
||
| Line 8: | Line 8: | ||
For each 1:1 replacement (full product gets a new TINP and the new TINP only refers to that product) deliver the new TINP for any TINT-specific tag-set. | For each 1:1 replacement (full product gets a new TINP and the new TINP only refers to that product) deliver the new TINP for any TINT-specific tag-set. | ||
==Tagger format string== | |||
* | * Choose tag name: | ||
** tinp_new - different meaning, e.g. could be new TINP that is not a replacement | |||
** tinp_replacement | |||
* create tag "tinp_replacement" | |||
** Done in 1.3.5 | |||
==Database changes== | |||
* create table "tinp_deprecation" | |||
** Done. | |||
==Database | |||
Revision as of 2013-03-03T00:57:13
P R O P O S A L
This is related to TINP fix.
Proposal:
- store the new TINP values in the DB
- deliver them via the tagger
For each 1:1 replacement (full product gets a new TINP and the new TINP only refers to that product) deliver the new TINP for any TINT-specific tag-set.
Tagger format string
- Choose tag name:
- tinp_new - different meaning, e.g. could be new TINP that is not a replacement
- tinp_replacement
- create tag "tinp_replacement"
- Done in 1.3.5
Database changes
- create table "tinp_deprecation"
- Done.