| 5 | * If the current item has a default value for the annotation, the default value should be removed. |
| 6 | * The default value should be copied to project-specific annotations. One for each release that the item (and annotation type) is part of. |
| 7 | * If the item doesn't have a default value, nothing should be done. |
| 8 | * Already existing project-specific values should not be modified. |
| 9 | |
| 10 | For example: |
| 11 | |
| 12 | * Item A is part of release 1.0, 1.1 and 2.0. |
| 13 | * It has a default annotation value: `foo=bar` |
| 14 | * In release 3.0 the value has been removed. |
| 15 | * The default value is removed and three new project-specific values for 1.0, 1.1 and 2.0 is created: `foo=bar`. |
| 16 | |
| 17 | * Item B is part of release 1.0, 1.1 and 2.0 |
| 18 | * It has a default value: `foo=bar` and a project-specific values for 1.1 and 2.0: `foo=bar2`. |
| 19 | * In release 3.0 the value has been removed. |
| 20 | * The default value is removed and one new project-specific value for 1.0 is created: `foo=bar`. The project-specific values for 1.1 and 2.0 are not modified. |