stackabletech / stackabletech/docker-images
tracking: Update major/minor versions for 26.11.0
Open
Nobody has claimed this yet.
epic
scheduled-for/26.11.0
- Dominant language
- Dockerfile
- Stars
- 22
- Forks
- 6
- Avg merge
- 16h 59m
- Merged PRs (30d)
- 30
Description
Part of https://github.com/stackabletech/issues/issues/889.
Tooling updates
[!TIP]
- Rust version bump
- Cargo dependency bumps
- Cutting a release and using that in docker-images.
- containerdebug
- config-utils
Items which don't have a tracking issue
- protoc updated in UBI Builder Dockerfiles (The earlier the better)
- jmx_exporter (validate via hdfs-operator smoke tests)
- krb5
- tools (update the versions in version.py)
- testing-tools (update the base, maybe keycloak)
- statsd: https://github.com/stackabletech/docker-images/pull/1664
- csi-provisioner for secret-operator
- csi-provisioner for listener-operator
- git-sync --> mirrored 4.7.1
Product Container Images
- https://github.com/stackabletech/docker-images/issues/1642
- https://github.com/stackabletech/docker-images/issues/1643
- https://github.com/stackabletech/docker-images/issues/1644
- https://github.com/stackabletech/docker-images/issues/1645
- https://github.com/stackabletech/docker-images/issues/1646
- https://github.com/stackabletech/docker-images/issues/1647
- https://github.com/stackabletech/docker-images/issues/1648
- https://github.com/stackabletech/docker-images/issues/1649
- https://github.com/stackabletech/docker-images/issues/1650
- https://github.com/stackabletech/docker-images/issues/1651
- https://github.com/stackabletech/docker-images/issues/1652
- https://github.com/stackabletech/docker-images/issues/1653
- https://github.com/stackabletech/docker-images/issues/1654
- https://github.com/stackabletech/docker-images/issues/1655
- https://github.com/stackabletech/docker-images/issues/1656
- https://github.com/stackabletech/docker-images/issues/1657
- https://github.com/stackabletech/docker-images/issues/1658
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
Start with the linked parent issue and child issues 1642–1658, then review version.py for tools and the UBI Builder Dockerfiles for the protoc update. Validate jmx_exporter through HDFS operator smoke tests; done means the listed tooling and product-image checklist items are completed and tracked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dockerfile, rust
- Domain
- build-system, devops, release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100