stackabletech / stackabletech/operator-rs

tracking: Prepare stackable-versioned for publication

Open
#852 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
167
Forks
19
Avg merge
1d 6h
Merged PRs (30d)
9

Description

This tracks the work required in stackable-versioned before being made available as a standalone crate for the Rust community.

  • Provide support for SemVer (instead of K8s API versions)
  • Provide support for generic versioning (types need to support Ord, FromStr, ...)
  • Enable deprecated prefix requirement only when using K8s features (see #864 (comment))
  • Cleanup documentation

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by auditing the stackable-versioned crate and the four checklist items in this issue; the discussion linked from PR #864 is relevant to the deprecated-prefix requirement. Determine the existing versioning and documentation entry points, then verify that SemVer, generic versioning, conditional prefix handling, and documentation cleanup are all complete.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, rust
Domain
devops, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.