hyperledger-labs / hyperledger-labs/fabric-operator
Implement semantic revisioning and release practices for the operator
- Dominant language
- Go
- Stars
- 78
- Forks
- 47
- Avg merge
- 1h 24m
- Merged PRs (30d)
- 3
Description
Implement [Semantic Version](https://semver.org) and a proper release practice for fabric-operator.
- Generate GitHub "release builds" of the operator, associated with release tags
- Write a script, or document the process for _turning a release_ (bumping major, minor, or patch levels)
- publish proper labels for artifact images:
```
# main line build outputs:
ghcr.io/hyperledger-labs/fabric-operator:latest
# release line build outputs:
ghcr.io/hyperledger-labs/fabric-operator:v${major}.${minor}
ghcr.io/hyperledger-labs/fabric-operator:v${major}.${minor}.${patch}
ghcr.io/hyperledger-labs/fabric-operator:v${major}.${minor}.${patch}-${git-commit-short-hash}
```
Contributor guide
Research direction
Start by locating the operator's current build, image-publishing, and release configuration; the issue names no files or tests. Establish how tags and GitHub release builds should be produced, then verify that main-line and versioned image labels match the listed formats and that the documented release process covers major, minor, and patch bumps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github, go
- Domain
- devops, infrastructure, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100