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

Prerelease option added #452

Closed
wants to merge 1 commit into from
Closed

Conversation

mguptahub
Copy link

@mguptahub mguptahub commented Sep 4, 2024

Users have an option to mark as PreRelease=true when required.

In my case, build from main branch is marked latest, v/s build from other branches are marked as prerelease

@mguptahub
Copy link
Author

@cpanato - Can you help with reviewing this PR ?

@cpanato
Copy link
Member

cpanato commented Oct 30, 2024

Sorry for the delay, @mguptahub. I will take a look.

@PrivatePuffin I do those things in my free time and for free; if you want to help, please step up instead of complaining without knowing what happens behind the scenes

@cpanato
Copy link
Member

cpanato commented Oct 30, 2024

@mguptahub can you rebase to get the latest changes and trigger ci?

@helm helm deleted a comment from PrivatePuffin Oct 30, 2024
@PrivatePuffin
Copy link

PrivatePuffin commented Oct 30, 2024

@PrivatePuffin I do those things in my free time and for free; if you want to help, please step up instead of complaining without knowing what happens behind the scenes

You dont have to explain how opensource maintainership works. I am in the same situation and also dont have time to spend beyond the projects I'm already maintaining.

I'm indeed looking for some free time to spend on Helm for the last year or so.
Specifically, filing a formal request with the CNCF either step in and put their millions of funding to actually use or void the Helm CNCF status (like they did for OpenEBS already) and admit the CNCF is failing in keeping important cloud-infrastructure project alive.


part of the reason why I dont have the time to spend on Helm, is that we had to develop a boatload of new CI/CD tooling to work around the issues Chart-Releaser, Chart-Testing etc are having.

Which is not an attack btw, but I cannot both compensate by writhing new tooling AND fixing current tooling which would end up in your PR pipeline.

@mguptahub
Copy link
Author

@cpanato I was forced to create a new PR as could not reopen this PR #468

Can you please look into it and suggest if any changes are required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants