openmainframeproject / openmainframeproject/software-discovery-tool
General Housekeeping tasks - release cycle
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 41
- Forks
- 50
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 3
Description
### Tasks
- [ ] To start proper release cycle, we need to get automations and deployments fixed first and foremost.
- [ ] introducing Docker (#223 WIP)
- [ ] introducing auto submodule update (#222 review)
- [ ] pre build checks - check if env/config files are set correctly before building docker
- [ ] run.sh and build.sh separately for updating docker environment for testing
- [ ] automation of all the above (typically one deployment per release cycle)
- [ ] update documentation after all the above (chronological disaster at the moment)
- [ ] Further discussions on #211
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
Start by reviewing #223 and #222, then inspect the existing run.sh, build.sh, environment/config handling, and the discussion in #211. Map the listed deployment and pre-build tasks before changing anything. Done means the release-cycle automation works, the Docker workflow is documented, and the remaining checklist items are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- build-system, ci-cd, devops, documentation, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100