Re: [Discuss][VOTE] Release Apache Log4j Tools 0.4.0

2023-07-04 Thread Volkan Yazıcı
Indeed I should have had an RC2 in the email subject, my mistake. All the rest of the information is correct. Due to the difference in the shared commit IDs, it is clear that this VOTE email and the previous one don't point to the same release, even though RC2 is not explicitly mentioned. I propose

Re: [More discussion][VOTE] Release Apache Log4j Tools 0.4.0

2023-07-04 Thread Volkan Yazıcı
Closed the Nexus repo. Will create a JIRA ticket for the Legal to update the release policy. On Tue, Jul 4, 2023 at 8:20 AM Ralph Goers wrote: > > I have verified the artifact in the distribution directory. It looks fine. > > I am hesitant to vote on this though as you have not closed the releas

Re: [More discussion][VOTE] Release Apache Log4j Tools 0.4.0

2023-07-04 Thread Volkan Yazıcı
Created LEGAL-647[1]. Note that INFRA recommends[2] and explains[3] this technique too. [1] https://issues.apache.org/jira/browse/LEGAL-647 [2] https://infra.apache.org/release-publishing.html#signing [3] https://infra.apache.org/release-signing.html#automated-release-signing On Tue, Jul 4, 2023

Re: Creating "the distribution" via BeanShell

2023-07-04 Thread Volkan Yazıcı
See my comments inline below. On Mon, Jul 3, 2023 at 6:33 PM Ralph Goers wrote: > While I have no issue with the logic of what is being done I do object to using BeanShell to do it. This smacks of going back to Ant/Make and “rolling your own”. It is also way too tempting for people to just go and