That seems like it could confuse users to me. The docs will refer to feature X being in version Y of the application — how do I connect that to a helm chart? Or if I want to go read the source code that’s connected to the helm chart I’m running, where do I find that mapping?
Couldn’t we just cut a patch version of the source and do a release (binary + helm chart) so that there’s always a clear coupling? On Thu, Jan 30, 2025 at 10:44 AM Dmitri Bourlatchkov <di...@apache.org> wrote: > Hi All, > > PR 912 [1] prompted this discussion. > > I believe it is valuable to release helm charts separately from the main > source / binary bundle primarily because the lifecycle of the charts is > different from java code and often requires changes that are not connected > to service implementations. > > I'd like to propose: > > * Each binary java release to have a matching Helm chart release with > possibly a different version. > > * Allow independent helm chart releases. > > * Source releases (e.g. 0.9) do not have to be connected to any particular > helm chart release. > > Thoughts? > > [1] https://github.com/apache/polaris/pull/912 >
