openmainframeproject / openmainframeproject/software-discovery-tool
Add releases to the project
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 41
- Forks
- 50
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 3
Description
One mark of maturity of a project is starting to make releases, where certain expectations exist for the project, including not making major breaking changes without warning or documentation. Recent examples are things like the back-end replacement, changing how we manage secrets and configuration files, and the upcoming UI overhaul.
We should start thinking about starting to do releases and documenting accordingly.
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
The issue names no files, tests, or entry points. Start by clarifying the project's release expectations around breaking changes, backend replacement, secrets, configuration files, and the UI overhaul. Done should include an agreed release process and corresponding documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100