OpenBankProject / OpenBankProject/OBP-API
Tag releases
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.7k
- Forks
- 482
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 15
Description
Which branch / tag is considered stable, the develop branch?
I propose we setup releases for OBP-API https://github.com/OpenBankProject/OBP-API/tags so that people are not confused thinking there hasn't been a release since 2016. Let's give people confidence by tagging and releasing which can be achieved trivially by tagging upon merge. Let's do it?
Context: Writing & testing deployment docs for Openshift but OBP-API is missing release tags
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
Start with the OBP-API tags page and the issue's question about whether develop is stable; compare the existing tags with the deployment documentation context from OBP-Kubernetes issue 6. Define which branch is stable and what release tags should be created on merge. Done means the release convention is established and the missing releases are tagged clearly enough for deployment documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100