Release Process Cleanup: Cloud Controller Manager
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation, release
Research direction
Start by checking whether a top-level CONTRIBUTING.md exists, then inspect .github/ISSUE_TEMPLATE/release_checklist.md and other release-related templates, keeping release.yaml. Consolidate their release instructions in CONTRIBUTING.adoc, preserving any needed contribution guidance; done means the release process has one documented location and obsolete release templates are removed.
Written by the indexing model from the issue text.
Description
Let's clean up the release process across our repositories so that the release process is documented in a consistent location.
- Create a top-level
CONTRIBUTING.adocfile. If there's an existingCONTRIBUTING.mdfile, rename it toCONTRIBUTING.adoc. - Document the release process in a new or existing section within
CONTRIBUTING.adoc. - Delete the
.github/ISSUE_TEMPLATE/release_checklist.mdfile and any other issue templates that have to do with releasing except forrelease.yaml. Be sure to synthesize the instructions from these deleted files intoCONTRIBUTING.adoc.
- Dominant language
- Go
- Stars
- 6
- Forks
- 2
- Avg merge
- 2h 37m
- Merged PRs (30d)
- 11
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from oxidecomputer/oxide-cloud-controller-manager
-
Documentation Kubernetes Cloud Controller Manager (CCM)
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
oxidecomputer/oxide-cloud-controller-manager#279 ·
Maintainers usually reply within 1 day
-
Documentation Kubernetes Cloud Controller Manager (CCM)
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
oxidecomputer/oxide-cloud-controller-manager#278 ·
Maintainers usually reply within 1 day
-
Bug Kubernetes Cloud Controller Manager (CCM)
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oxidecomputer/oxide-cloud-controller-manager#276 ·
Maintainers usually reply within 1 day
-
Bug Kubernetes Cloud Controller Manager (CCM)
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oxidecomputer/oxide-cloud-controller-manager#275 · 1 comment ·
Maintainers usually reply within 1 day
-
Enhancement Kubernetes Cloud Controller Manager (CCM)
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
oxidecomputer/oxide-cloud-controller-manager#274 ·
Maintainers usually reply within 1 day
All issues in oxidecomputer/oxide-cloud-controller-manager
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
521xueweihan/HelloGitHub#3789 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 12 days
-
stage-fail
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
siyuan-note/bazaar#2282 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openshift/kube-compare#307 ·
Maintainers usually reply within 1 day