https://www.apache.org/legal/release-policy.html#release-approval <https://www.apache.org/legal/release-policy.html#release-approval>
I think it’s entirely appropriate that I ask why you are not following the well known: `Release votes SHOULD remain open for at least 72 hours.` To me this means that any shorter release vote needs a good justification. What does it mean to you? You say it’s not a critical release, so what’s the hurry? David Jencks > On Dec 19, 2021, at 9:40 AM, Andrea Cosentino <anco...@gmail.com> wrote: > > It's not a critical release i meant to say > > Il dom 19 dic 2021, 18:36 Andrea Cosentino <anco...@gmail.com> ha scritto: > >> It's a critical release and we already done it in the past. If you any >> troubles we could extend to 72 hours. But i don't see why. For some sub >> projects we use 48 hours. >> >> It looks to me you're looking for problems where they don't exist. >> >> Let's do 72 hours. I don't want complaints. >> >> Il dom 19 dic 2021, 18:29 David Jencks <david.a.jen...@gmail.com> ha >> scritto: >> >>> What justifies the shorter-than-standard-72-hours voting window? >>> >>> David Jencks >>> >>>> On Dec 19, 2021, at 1:27 AM, Andrea Cosentino <anco...@gmail.com> >>> wrote: >>>> >>>> I'll release tomorrow morning and open a vote for 48 hours, since this >>> will >>>> be outside camel-k. >>>> >>>> Il sab 18 dic 2021, 10:05 Claus Ibsen <claus.ib...@gmail.com> ha >>> scritto: >>>> >>>>> Hi >>>>> >>>>> I think it would be good to get a new release of kamelets that works >>>>> well with the new Camel 3.14.0 release. >>>>> >>>>> We did some updates to the yaml-dsl in 3.14 that requires a new >>>>> release of kamelets to work. >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Claus Ibsen >>>>> ----------------- >>>>> http://davsclaus.com @davsclaus >>>>> Camel in Action 2: https://www.manning.com/ibsen2 >>>>> >>> >>>
