potiuk commented on issue #292: URL: https://github.com/apache/tooling-trusted-releases/issues/292#issuecomment-3492451352
> 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. We can't realy do it with 00005 -> we are followign strict python versioning rules from https://peps.python.org/pep-0440/#public-version-identifiers and we **MUST** tag our releases with rcN if we want to upload it to PyPI. I think maintaining mapping of revision -> rc candidate should be in the ATR - also in our release emalis we are linking to PyPI Urls where people can download the releaseses from or look at documentation/changelogs - so that would be way more convenient. > A4: Surprisingly there is no REVISION variable that you can use yet. This is a great suggestion, thanks. I've created https://github.com/apache/tooling-trusted-releases/issues/295 to track this. I guess we need SUFFIX or TAG :) as well if we add manual way of marking the release. -- 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]
