sbp commented on issue #292: URL: https://github.com/apache/tooling-trusted-releases/issues/292#issuecomment-3492407573
Thanks for explaining this in such detail! A1: I think that you should use `0.1.0`, because the version number in ATR that it tracks through the releasing process is the version number that will be used for the final release. The `rc1` suffix seems to be something that you're introducing to distinguish between separate voting phases. I acknowledge this; more on this below. A2: There currently isn't a way to do this. We use the format "NNNNN" for revisions, such as "00005". You probably don't want to do "CTL 0.1.0 from 00005", but maybe? The advantage here is that 00005 uniquely identifies a revision within ATR so you know exactly what you're voting on. However, obviously "rc1" is clearer. Therefore I think the ability to effectively "tag" revisions in ATR is a good one. Please let me know if 00005 would be sufficient, or whether you'd prefer to alias revisions so that e.g. rc1 -> 00005. A3: Yes, uploading always replaces. You can always restore files from previous revisions without having to have saved local copies. A4: Surprisingly there is no `REVISION` variable that you can use yet. This is a great suggestion, thanks. I've created #295 to track this. A5: Not applicable because the version should be `0.1.0`. Please let me know if there is anything that I did not cover. -- 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]
