Thank you Rui, sounds good!
Gyula
On Fri, Oct 20, 2023 at 11:14 AM Rui Fan <1996fan...@gmail.com> wrote:
> Hi devs,
>
> I checked all commits that the main branch has but release-1.6 branch
> doesn't,
> all of them are improvements instead of bug fixes. So I will prepare the
> 1.6.1-rc1 based on
Hi devs,
I checked all commits that the main branch has but release-1.6 branch
doesn't,
all of them are improvements instead of bug fixes. So I will prepare the
1.6.1-rc1 based on the latest release-1.6 branch.
Please let me know if any critical commit is missed at release-1.6 branch,
thanks~
An
Thanks Rui,
I would appreciate your help. Let's sync on the tasks offline.
As for the bugfix commits. We can take a quick look and backport some other
fixes if needed but we should focus on critical fixes / regressions to make
the changes minimal given that the 1.7.0 is not so far anyway :)
Cheer
Hi Gyula,
Thank you for driving this discussion!
This release seems good to me, I have a question:
I see some bugfix commits have been merged into
the 1.6-release branch. Does it already contain all
recent bugfix commits?
Also, you said in the `Kubernetes Operator 1.6.0 release planning`[1]:
>
Hi All!
I would like to propose to release the 1.6.1 patch version for the
Kubernetes operator. The release branch currently contains 2-3 critical
fixes for issues that many users have hit over time.
Making this release now would allow us more time to wrap up and finalize
the 1.7.0 release change
