For many projects, especially "library" projects, the "convenient binaries" that matter most these days are the jars (source, binary, and javadoc) that are deployed to the maven repo. Calcite releases in fact do not currently include a binary tar ball, only a source tar ball and maven jars.
Are these jars subjected to due diligence during the release vote? It seems to me that each of those jars is a de facto binary release. (Not that I think there is too little due diligence! We've been on the receiving end of a fair amount recently.) Julian On Oct 13, 2014, at 10:02 AM, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > On Mon, Oct 13, 2014 at 3:54 PM, Ted Dunning <ted.dunn...@gmail.com> wrote: >> On Mon, Oct 13, 2014 at 7:51 AM, Bertrand Delacretaz <bdelacre...@apache.org >>> wrote: >>> ....make sure >>> podlings understand the difference between source code releases and >>> convenience binaries. >>> >> Based on recent discussion, a review of this distinction would be valuable >> for many at Apache. > > Aren't these pages sufficient for that? > > http://apache.org/dev/release.html (search for "bina") > http://www.apache.org/dev/licensing-howto.html#binary > > Otherwise I'd suggest adding an "about convenience binaries" section > at http://apache.org/dev/release.html with a small set of relevant > questions and answers. > > -Bertrand > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
