>From what I have learned from the last 1.0.0 release, I think it is not too
complicated and a big burden for flink-kubernetes-operator patch releases.
The major bottleneck might be the VOTE duration(e.g. jet lag, the weekend).
We almost need one week for the release after all the blockers are reso
My bad, our bylaws actually state that release votes must have a minimum
3 days duration.
On 14/06/2022 14:46, Chesnay Schepler wrote:
Yes, pretty much.
Mind you that the 72h voting duration is a recommendation by the ASF;
it's not a strict rule.
AFAICT we also haven't locked this down in our
Yes, pretty much.
Mind you that the 72h voting duration is a recommendation by the ASF;
it's not a strict rule.
AFAICT we also haven't locked this down in our bylaws, apart from
requiring 3 votes.
On 14/06/2022 14:25, Gyula Fóra wrote:
I think what you are referring to is here:
https://www.a
I think what you are referring to is here:
https://www.apache.org/legal/release-policy.html#source-packages
Based on this we probably cannot simply release the docker image. We could
decide to not release the maven artifacts though, but that seems to be a
minor difference and probably not worth it
Thanks Chesnay, these are exactly the questions I would like to clarify
because I don't really understand the limitations/boundaries of the apache
release process.
Is there a strict requirement to have a source release accompany the docker
image? I will have to look this up.
Gyula
On Tue, Jun 14
On 14/06/2022 14:10, Gyula Fóra wrote:
For the operator the main logic (and the bugs) are part of the operator
docker image and the helm charts associated with it. It would be nice to be
able to have lightweight patch releases that only contain the docker
image + updated Helm chart.
This would a
On 14/06/2022 14:10, Gyula Fóra wrote:
Another alternative would be to simply not have these patch releases and
encourage users to pick up the latest automatic image builds from
https://ghcr.io/apache/flink-kubernetes-operator for the current release
branch, but I feel that production users woul
Hi Devs!
I would like to discuss/propose a new release flow for the Kubernetes
operator patch releases.
For the operator the main logic (and the bugs) are part of the operator
docker image and the helm charts associated with it. It would be nice to be
able to have lightweight patch releases that
