mirror of
https://github.com/Stone-Red-Code/dvc.git
synced 2026-11-02 07:18:25 +01:00
Oded Messerandpre-commit-ci[bot]
d1c5fcc1b8
* Add template * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
1.3 KiB
1.3 KiB
name, about, title, labels, assignees
| name | about | title | labels | assignees |
|---|---|---|---|---|
| Epic/Story Issue Template | Template for "top" level issues - Epics (>2 weeks) / Stories (<2 weeks) | Epic: New Feature | epic |
Summary / Background
What do you want to achieve, why? business context ...
Scope
What will be impacted and what won't be? What needs implementation and what is invariant? e.g.
- user should be able to run workflow X from UI
- enable workflow Y, Z from CLI
Assumptions
Product / UX assumptions as well as technical assumptions / limitations e.g.
- Support only Python Runtime
- Focus on DVC experiments only
- Deployment environments don't change often and can be picked up from shared configuration
Open Questions
e.g.
- How should access control work for shared artifacts (workflow X)
- Python runtime assumption - is it really valid? in light of <...>
Blockers / Dependencies
List issues or other conditions / blockers
General Approach
Invocation example:
$ mapper-run task.tar.gz --ray-cluster <ip>:<port>
Steps
Must have (p1)
- subissue2
- step 2
- info
- info
Optional / followup (p2)
- ⌛ step 3 wip
- step 4
Timelines
Put your estimations here. Update once certainty changes
- end of week (Feb 3) for prototype with workflows X, Y
- Feb 15 - MVP in production
- Low priority followups can be done later