I added my key to the KEYS file in the svn repo one level up.. Gesendet von Outlook für Android<https://aka.ms/AAb9ysg> ________________________________ From: Peter Hunsberger <peter.hunsber...@gmail.com> Sent: Sunday, October 29, 2023 6:16:02 PM To: dev@cocoon.apache.org <dev@cocoon.apache.org> Cc: Cocoon PMC List <priv...@cocoon.apache.org> Subject: Re: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/
Everything looks good except I can't check the signature, I get "No public key" from gpg. I believe I need a copy of your public key to import? Peter Hunsberger On Sun, Oct 29, 2023 at 6:55 AM Christofer Dutz <christofer.d...@c-ware.de<mailto:christofer.d...@c-ware.de>> wrote: Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote on accepting it for release. All Maven artifacts are available under [1]. Voting will be open for 72hr. A minimum of 3 binding +1 votes and more binding +1 than binding -1 are required to pass. Release tag: https://svn.apache.org/viewvc/cocoon/tags/cocoon-2.3/cocoon/cocoon-2.3.0/ Director revision of the tag: 1913422 Per [3] "Before voting +1 PMC members are required to download the signed source code package, compile it as provided, and test the resulting executable on their own platform, along with also verifying that the package meets the requirements of the ASF policy on releases." You can achieve the above by following the guide of a fellow Apache project [4]. [ ] +1 accept (indicate what you validated - e.g. performed the non-RM items in [4]) [ ] -1 reject (explanation required) [1] https://repository.apache.org/content/repositories/orgapachecocoon-1007 [2] https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/ [3] https://www.apache.org/dev/release.html#approving-a-release [4] https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
