Jyyjy commented on issue #58: URL: https://github.com/apache/flagon/issues/58#issuecomment-2689284497
I wouldn't say it's intended, but I don't think excluding build/ violates [Apache policy](https://www.apache.org/legal/release-policy.html#artifacts). I'm not opposed to changing the release process such that future releases include build/ in src, but I would oppose patching 2.4.0 just to include build/. There's two main release artifacts, the src archive and the bin archive. And there's two main places where you would download these artifacts, [Apache](https://downloads.apache.org//flagon/useralejs/2.4.0/) and [GitHub](https://github.com/apache/flagon-useralejs/releases/tag/2.4.0). I see that there is no build/ in the src artifacts in either of these places. And the bin artifact is missing from the GitHub tag artifacts. There is an additional source code artifact generated by default in the GitHub tag artifacts that contains build/ because it is a simple snapshot of the repo. -- 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: notifications-unsubscr...@flagon.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@flagon.apache.org For additional commands, e-mail: notifications-h...@flagon.apache.org
