[New Process Improvement Need]: Tracing artifact versions with dependencies
Open
Nobody has claimed this yet.
low complexity
more requested
software lifecycle
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Checked for duplicates
Yes - I've already checked
Category
Software Lifecycle - the creation, change, and release of software
Describe the need
We have a need for:
- Best practices on cataloging versioning compatibility relationships among software, datasets, tools, etc.
- Process for maintaining multiple versions of algorithms (+1'd by @ramesh-maddegoda)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides no files, tests, or entry points to inspect. Start by defining the cataloging and version-compatibility requirements, then establish what documentation and process for maintaining multiple algorithm versions would count as complete.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100