[GitHub] [pulsar-helm-chart] michaeljmarshall commented on issue #185: Github Actions should enforce an increase in helm chart semantic version on each PR

[GitBox <gi...@apache.org>]

michaeljmarshall commented on issue #185:
URL: https://github.com/apache/pulsar-helm-chart/issues/185#issuecomment-1005897271


   I think a release for every change would lead to too many releases. However, there is an underlying problem that this issue points to: contributors to the helm chart feel that it can take too long to get a simple fix included in a release. As you mentioned, we use to only release the helm chart when Apache Pulsar was released. I'm not sure why we had the initial process, but I don't think we _need_ to synchronize releases of Pulsar and its official helm chart.
   
   We could add something to the README or to a CONTRIBUTORS file that indicates how we version the chart and explicitly lets contributors know how to request a release. Note that anyone wanting to initiate a release can open a PR to bump the version of the helm chart.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org