Version of package skeletons
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 151
- Forks
- 183
- Avg merge
- 14m
- Merged PRs (30d)
- 2
Description
Expected behavior
if a new ATLAS version is released I can find somewhere which version of the Skeleton packages are supported. This also requires proper versioning and releases of these skeletons.
Actual behavior
I have no idea what version of the skeleton is used when downloading the study package. The skeletons have no official releases (Prediction) and/or master is not used correctly as having the latest release but is 'miss-used' as a development branch.
Steps to reproduce behavior
NA
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Start by tracing how ATLAS downloads the study package and how the skeleton packages are currently versioned and released. Done should make the supported skeleton version discoverable for each ATLAS version and establish a clear release-versus-development-branch process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100