Correct me if I read you wrong: *"you have added a timestamp, so you can
update it to trigger the CI"*. Adding a timestamp creates an RM
responsibility. It adds one extra manual step to the release procedure. And
I am against this. (I think everybody should be against it.) Do you want to
trigger th
Hi Volkan,
On Thu, 19 Oct 2023 at 23:40, Volkan Yazıcı wrote:
>
> We shouldn’t manually provide a value each time. If you are adamant about
> it, we should ideally pass it from command line in CI workflow. But again,
> not manually please. This undermines our objective of relieving RM’s load.
Th
We shouldn’t manually provide a value each time. If you are adamant about
it, we should ideally pass it from command line in CI workflow. But again,
not manually please. This undermines our objective of relieving RM’s load.
On Thu, 19 Oct 2023 at 23:33, Piotr P. Karwasz
wrote:
> Hi Volkan,
>
> O
Hi Volkan,
On Thu, 19 Oct 2023 at 23:20, Volkan Yazıcı wrote:
>
> Piotr, why do we need this? We already inherit a valid value from parent’s
> parent, i.e., ‘org.apache:apache’.
We don't, but the build didn't start without a change.
On the other hand we should use a realistic value, not whatever
Piotr, why do we need this? We already inherit a valid value from parent’s
parent, i.e., ‘org.apache:apache’.
On Thu, 19 Oct 2023 at 19:35, wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> pkarwasz pushed a commit to branch release/2.21.1
> in repository
> https:
