hboutemy commented on issue #117: URL: https://github.com/apache/tooling-trusted-release/issues/117#issuecomment-2955591886
I'm introspecting why even myself, I did not create DOAP files for Maven's 80 projects even if I'm involved in p.a.p for more than 10 years, but I created 40 ATR sub-projects in 15 minutes one aspect I'm discovering is that most DOAP attributes would make sense to store in the project's Git repo, done once for all times for each project BUT the release data aspect of DOAP file is what is causing recurring updates (after each release), and what makes the 2 Maven (Committee) existing DOAP files a pain to maintain (and probably a bad choice of having stored them in their original Git repositories) in the future, if we keep DOAP as a format, we'll need to clarify/automate release update workflow, vs everything else that is more human work to be done once... -- 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
