It has been said many times that Apache does not do binary releases, only source releases. But users like binary releases (or pre-built binary artifacts, if you prefer), and therefore podlings like to create them.
So, is there any guidance for how to review a release that contains source and binary tar-balls. Take, for example, crail-1.1-rc2[1], which contains both a -src.tar.gz and a -bin.tar.gz. -rw-rw-r-- 1 jhyde jhyde 28115272 Oct 23 11:25 apache-crail-1.1-incubating-bin.tar.gz -rw-rw-r-- 1 jhyde jhyde 473 Oct 23 11:25 apache-crail-1.1-incubating-bin.tar.gz.asc -rw-rw-r-- 1 jhyde jhyde 169 Oct 23 11:25 apache-crail-1.1-incubating-bin.tar.gz.sha512 -rw-rw-r-- 1 jhyde jhyde 1706869 Oct 23 11:25 apache-crail-1.1-incubating-src.tar.gz -rw-rw-r-- 1 jhyde jhyde 473 Oct 23 11:25 apache-crail-1.1-incubating-src.tar.gz.asc -rw-rw-r-- 1 jhyde jhyde 169 Oct 23 11:25 apache-crail-1.1-incubating-src.tar.gz.sha512 As a reviewer, how am I to vote on this release candidate? Should I vote -1 because the RC contains binaries? Should I ignore the -bin.tar.gz and just vote based on the -src.tar.gz? Or are there some review steps I should apply to the -bin.tar.gz? If this policy is documented somewhere, please send me the link, but I couldn’t find it. Julian [1] https://dist.apache.org/repos/dist/dev/incubator/crail/1.1-rc2/ --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
