dave2wave opened a new issue, #34: URL: https://github.com/apache/tooling-trusted-release/issues/34
I decided to make a test release in Tooling using the Pulsar KEYS file which was already loaded. When I did all of the keys were rejected as duplicates. I then went ahead and uploaded the files to start composing the draft. The checks for the asc file failed which tells me that the keys were never associated, We can proceed in two ways. KEYS files are additive for all once, or a key is associated with as many projects as desired. The former is easier because we eliminate code while the latter is more explicit. Perhaps we should consider what we might do in the beta when we do releases. We will need to automate the update of the committee's KEYS file -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org For additional commands, e-mail: dev-h...@tooling.apache.org
