Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release more often? #567

Open
sbp-bvanb opened this issue Mar 12, 2025 · 3 comments
Open

Release more often? #567

sbp-bvanb opened this issue Mar 12, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@sbp-bvanb
Copy link

0.12.0 has been released more than a year ago? Could you release it at least once a month?

@sbp-bvanb sbp-bvanb added the bug Something isn't working label Mar 12, 2025
@polarathene
Copy link

#553

@sbp-bvanb
Copy link
Author

sbp-bvanb commented Mar 13, 2025

Then put it to read-only, i.e. archive it to provide clarity.

@polarathene
Copy link

Then put it to read-only

I can't do anything, it's up to @wagoodman how to handle it.

I have been using this fork which is compatible with the containerd image store:

docker run --rm -it \
  --volume /var/run/docker.sock:/var/run/docker.sock \
  --security-opt label:disable \
  ghcr.io/joschi/dive:latest \
  alpine

That developer does not want to maintain the fork however. @wagoodman is cautious to transfer ownership of the repo which is fair, but perhaps might consider migrating dive to an organization and allowing the existing fork maintainers some ability to help maintain the project going forward. So far they've not done anything malicious 🤷‍♂ (and users will end up using various forks over time as dive here becomes less compatible with modern tooling, which is arguably worse for users than an organization @wagoodman could still have influence over)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants