[DIDM-4] Use MD-SAL models Created: 15/Feb/16 Updated: 19/Oct/17 |
|
| Status: | Confirmed |
| Project: | didm |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | A H | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 5357 |
| Description |
|
Use MD-SAL models yangtools models have been long obsoleted, use mdsal ones. |
| Comments |
| Comment by A H [ 15/Feb/16 ] |
|
Patch available: |
| Comment by A H [ 15/Feb/16 ] |
|
Severity: Could you elaborate on the severity of this bug? Is this a BLOCKER such that we cannot release Beryllium without it? Is there a workaround such that we can write a release note and fix in Beryllium SR1? |
| Comment by Robert Varga [ 15/Feb/16 ] |
|
Severity: This is a build-time consistency issue, DIDM pulling in old artifacts during the build (and unit tests). Runtime is not affected, as it will bring in the new models and bindings via md-sal features. Hence this does not block the release, I do not think we need to even release-note it. It is just something we want to fix so it does not explode on us in the future. Testing: As this is build-time issue, Jenkins verification is enough. Impact: I do not believe this has any impact outside of DIDM. |