sbp commented on issue #136: URL: https://github.com/apache/tooling-trusted-release/issues/136#issuecomment-2962987378
ASF committees use a variety of organisational methods for their releases at present, but ATR has a very strict organisation method where each release gets one dedicated directory in the `unfinished` tree. When a committee performs final publication of the release, we preserve that structure by moving it to the `finished` tree. If we're to make the downloads directory URL flexible in the manner described in this issue, replicating the situation on dist today to help projects to transition to ATR, then it may be prudent instead to retain `finished` with the ATR structure and to create a new `downloads` tree with hard links to files in `finished`. This would help us to keep a very strict, logical record of what was voted on by the committee, and what the state of the files was at release. It would also allow us to undo any problems with colliding files between releases, reconsiderations after publication, etc. It keeps a record of the provenance of every file as long as `finished` is read only, as originally intended by design. -- 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 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
