hboutemy commented on issue #117: URL: https://github.com/apache/tooling-trusted-release/issues/117#issuecomment-2953586307
on infering subprojects by looking at released artifacts: there are quite a few patterns recognizable by humans, but getting a solid classification will IMHO not be easy just at Maven level, we defined 2 types of release forms: 1. basic "source-release.tar.gz" 2. "src+bin" (like Maven core https://dist.apache.org/repos/dist/release/maven/maven-3/3.9.10/ ) and even with quite a good consistency on there 2 patterns, when we worked at checking our releases, I went down a path of describing our many subprojects though a handwritten conf file = https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/dist-tool.conf.html doing the same with more diversity of practices and with automation won't be easy and deciding if the resulting is called a subproject or something else will be fun when we discuss about releases with variable scope like Airflow: but I expect that variable scope is an exception -- 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
