Do not display task document version numbers, other small fixes #90
Conversation
|
The changes look good, but I'm starting to rethink on the benefit of displaying the version numbers. As you mentioned in the ACCESS-CI slack channel, the version numbers were meant to be for both RPs and ACCESS to differentiate between significant documentation changes (e.g. if RP1 previously completed Taskv1 and ACCESS later creates Taskv2 to signify major document changes, then RP1 may be expected to additionally complete Taskv2). Since the numbering seems to be for both the RPs (i.e. public-facing) and ACCESS (i.e. internal-facing), I'm wondering if we should actually continue with your idea of displaying the version numbers that way we don't force RPs to need to be aware of the "internal-facing" (i.e. https://github.com/access-ci-org/Integration_Roadmaps). For now, I think it'd be good if we could continue discussing whether or not to display the version numbers outside of this PR, and change this PR's scope to simply be fixing the broken link for |
| The Integration Coordinator should enter and update their RP contacts in CiDeR as detailed in the task: | ||
|
|
||
| - [Infrastructure Description v2] (Infrastructure_Description_v2.md) | ||
| The Integration Coordinator should enter and update their RP contacts in CiDeR as detailed in the [*Infrastructure Description task*](Infrastructure_Description_v2.md). |
There was a problem hiding this comment.
As mentioned here, I think this should be the only change included in this PR so that we can separately discuss the "to display or not display" version numbers convo without halting the release of fixing the broken link.
The concierge team agreed to not display task version numbers in documents. See additional details in https://access-ci.atlassian.net/browse/CTT-359