Implement Semantic Versioning Using Tags
What problem(s) will it solve?
With 39IOSDET1 taking control of IDF content for execution next calendar year, there is a desire to mitigate the risks posed by pipeline iterations on live content as minor updates (typos, small changes) need to occur in the content.
Who is the intended user(s)?
The intended users of this feature would be 39IOSDET1 personnel.
Lay out the expected user experience
Given the existing pipeline structure used to render content, When tagging is implemented, Then 39IOSDET1 curriculum developers and maintainers to make iterative updates to the curriculum while having a 'frozen' version of the pipeline and associated content (mttl, scripts, baselines, and templates repos) to ensure the stability of content while IDF classes are in session.
Proposal
Per @Jason-Thomas recommendation, implement tagging to accomplish the desired end state identified above.
Further details
Permissions and Security
Documentation
Update User Documentation
- List any changes necessary to user documentation that this feature affects.
Update Developer Documentation
- List any changes necessary to developer documentation that this feature affects.
Update CYT Overview briefing
- Update overview slides relevant to this feature.
-Is there any other documentation affected?
Availability & Testing
What does success look like, and how can we measure that?
Success Metrics/Criteria
Acceptance Criteria
- Tagging is implemented
- Changes to curriculum content in 39IOSDev space are unaffected by new pipeline features
- A mechanism for version upgrade is available/planned