Conversation
Adds documentation that explains how we think about releases of the application and Helm Charts and when we will bump major, minor and patch versions for both Application and Chart Releases. Issue temporalio#264 Signed-off-by: Jay Pipes <jay.pipes@temporal.io>
|
|
| Likewise, We bump the patch version number of the Application Release version | ||
| when bug fixes are added to the controller code itself. |
There was a problem hiding this comment.
if we release a bug fix to the controller code itself, will we also cut a patch of the corresponding Helm Release so that users can install the bug fix via Helm?
This section made me concerned that maybe we would patch the image and not package that bug fix into a helm chart.
To take a step back, my understanding is that because many users install this code via Helm, whenever we release new controller code, we will always release it in some Helm Chart Version. And also if we change the chart but not the controller code, we might release a new Helm Chart Version. Are there cases where we would release new code but not put it in any Helm Chart release?
There was a problem hiding this comment.
overall looks good though! just want to make sure I understand this and we are communicating clearly
3 participants
Adds documentation that explains how we think about releases of the application and Helm Charts and when we will bump major, minor and patch versions for both Application and Chart Releases.
Issue #264