ISSUE-18: Documenting dependencies with other groups
dependency tracking
Documenting dependencies with other groups
- State:
- CLOSED
- Product:
- Document life cycle (pre 2014 chapter 7, now chapter 6)
- Raised by:
- Steve Zilles
- Opened on:
- 2013-06-10
- Description:
- In “SHOULD (was must for CR+ in 7.2) report any changes in dependencies with other groups.” Two issues:
a. Should this be a MUST or SHOULD? (Steve, Jeff 2)
b. Should there be an update on the status of dependency review and resolution. - Related Actions Items:
- No related actions
- Related emails:
- Re: tracker - please use it Re: List of issues on Chapter 7. (from karl@la-grange.net on 2013-06-10)
Related notes:
SteveZ: we need to define the basis from which changes are reported
Chaals: In resolving this issue, I expect to provide more detail about what kind of changes in dependencies we mean, and where to find them.
In draft https://dvcs.w3.org/hg/AB/raw-file/d97b11a76ac4/tr.html 2013-07-09 The requirement to document changing dependencies is a should, until LCCR where it is a must. Likewise for rescinding a recommendation dependencies have to be identified.
Charles 'chaals' (McCathie) Nevile, 18 Jul 2013, 23:24:32Display change log
