Re: [REQUEST] Grant permission to deploy Maven project via GitHub Actions

2023-07-03 Thread Greg Stein
Tison: STOP cross-posting between private and public lists. You have been advised to stop doing so once, and this is now TWICE. No more. Regards, Greg Stein Infrastructure Administrator, ASF On Mon, Jul 3, 2023 at 6:01 AM tison wrote: > Hi Daniel, > > Thanks for your information! That can be

Re: do we need to go through an Incubator PMC for a build tool?

2023-07-03 Thread Sheng Wu
Hi If we want that jar under asf package on maven central, yes, a new version is required a vote on dev first, then incubator. Meanwhile, if we have all mentors(ipmc members as well) voted, we just need to carry votes to incubator mail list, and another 3 days. Just one thing, if the jar has

Re: do we need to go through an Incubator PMC for a build tool?

2023-07-03 Thread PJ Fanning
Adding the Pekko mentors to the thread if that's ok. It's not a blocker for us to use a snapshot version of the Pekko-specific build tool but it would be tidier if we could release a stable version to Maven Central. If this requires us to release a source artifact via the full voting procedure

Re: [REQUEST] Grant permission to deploy Maven project via GitHub Actions

2023-07-03 Thread PJ Fanning
One of my Pekko colleagues found that this process is documented. I wasn't aware that this approach has been approved as long as the security team signs off. https://infra.apache.org/release-signing.html#automated-release-signing On Mon, 3 Jul 2023 at 12:04, tison wrote: > > Update mailing

Re: [REQUEST] Grant permission to deploy Maven project via GitHub Actions

2023-07-03 Thread tison
Update mailing list. Or if I should start a new thread totally? Best, tison. tison 于2023年7月3日周一 19:00写道: > Hi Daniel, > > Thanks for your information! That can be an alternative for the signing > key. > > Right now the blocker I met is 403 from the Nexus server which I suspect > is the lack

Re: [REQUEST] Grant permission to deploy Maven project via GitHub Actions

2023-07-03 Thread tison
Hi Daniel, Thanks for your information! That can be an alternative for the signing key. Right now the blocker I met is 403 from the Nexus server which I suspect is the lack of permissions from the Nexus credentials. Could you confirm or correct it? Best, tison. tison 于2023年7月3日周一 18:58写道: >

Re: [REQUEST] Grant permission to deploy Maven project via GitHub Actions

2023-07-03 Thread tison
Hi PJ, Thanks for sharing your thoughts! For signing key, it's a resolved topic from my perspective. I use - 1. A signing key commented with OPENDAL CODE AUTO SIGNING KEY[1] 2. Load the key from our 1password service, while since it's a specific key, I feel comfortable to pass it to INFRA

Re: [REQUEST] Grant permission to deploy Maven project via GitHub Actions

2023-07-03 Thread Daniel Gruno
On 2023-07-03 12:52, PJ Fanning wrote: Adding the Incubator general list. My view would be that non-snapshot binary artifacts should be signed with a personal signing key - ideally the signing key that was used to release the related source release. Unfortunately, this would mean adding a

Re: [REQUEST] Grant permission to deploy Maven project via GitHub Actions

2023-07-03 Thread PJ Fanning
Adding the Incubator general list. My view would be that non-snapshot binary artifacts should be signed with a personal signing key - ideally the signing key that was used to release the related source release. Unfortunately, this would mean adding a user's signing key to the Apache GitHub

Re: [VOTE] Release Apache OpenDAL(incubating) 0.38.0-rc1 - Incubator Vote Round 1

2023-07-03 Thread tison
+1 binding I checked - GPG sign matched - Checksum verified - LICENSE and NOTICE exist - DISCLIAIMER exists - Compile from source Best, tison. Xuanwo 于2023年7月3日周一 00:18写道: > Carry my non-binding vote from the OpenDAL Community: > > - [x] Download links are valid. > - [x] Checksums and