Hi Adam - I've added your key, please check and let me know if any issues. Regards Petri
________________________________ From: Adam Monsen <meonk...@apache.org> Sent: Tuesday, July 22, 2025 6:08 AM To: dev@fineract.apache.org <dev@fineract.apache.org> Subject: help needed with subversion for 1.12.1 release Hi all, I need help with the current release. There are a couple svn commands that must be run by a PMC member. One to add my release manager signing key, one to actually release (we won't do that until the release is approved). 1. copy dev KEYS file content from staging to release area 2. if/when 1.12.1 is approved, promote the release candidate to release area The first step can be done now. Basically we need https://dist.apache.org/repos/dist/dev/fineract/KEYS and https://dist.apache.org/repos/dist/release/fineract/KEYS to match. The content in dev/fineract/KEYS is correct. The content in release/fineract/KEYS needs my key so everyone can verify my signature with the release artifacts. One way to do this is: svn checkout --depth=files https://dist.apache.org/repos/dist/release/fineract/ cd fineract svn cat https://dist.apache.org/repos/dist/dev/fineract/KEYS > KEYS # diff should show additions of two lines, descriptions of my keys, # and my ascii-armored key data svn diff svn commit The --depth=files flag is handy to avoid getting copies of all subfolders and contents with the checkout. SHA-1 checksum of corrected KEYS file is b4dd51194ca50f653adb91eea4606c88758855d5. Please let me know if you're available to assist (with only step #1, for now), or just go ahead and do it. I think this is atomic... if two people try to do this, the 2nd person's attempt should fail gracefully. Best and thanks, -Adam PS - there's also a mechanism by which ASF Infra can grant committers access to the release area. I'm not sure we want to do that, I'm just mentioning for the sake of completeness.
