ppkarwasz opened a new issue, #171: URL: https://github.com/apache/tooling-trusted-release/issues/171
It appears that the current `Release` model uses a combination of project name and version number as its primary key. This design prevents storing multiple release candidates for the same version. Additionally, vote URLs are based solely on project name and version (e.g., `https://release-test.apache.org/vote/logging-log4j/2.25.0`). As a result, if one RC is deleted and another is created with the same version, the URL remains unchanged — leading to potential confusion. For example, I prematurely ended the first vote for Log4j 2.25.0 and started a second RC. Both votes shared the same URL, making it easy for voters to unknowingly cast votes on the newer RC thinking it was the original. ### Proposed Solution: Assign a unique UUID to each `Release` and incorporate it into the vote URL. This would: * Allow multiple RCs for the same version * Prevent voter confusion * Facilitate future integration with TEA (see #8) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
