It’s useful to clarify the terminology. There’s no such thing as a “binary release”. Release policy [1] says:
> Every ASF release MUST contain one or more source packages > All releases are in the form of the source materials needed to make changes > to the software being released. > > As a convenience to users that might not have the appropriate tools to build a > compiled version of the source, binary/bytecode packages MAY be distributed > alongside official Apache releases.” The binary packages that may accompany a release are generally referred to as “binary artifacts” of the release. Julian [1] https://www.apache.org/legal/release-policy.html#artifacts On Feb 8, 2023, at 7:19 AM, Dave Fisher <wave4d...@comcast.net> wrote: Hi PJ, Daffodil uses sbt and produces binary releases - https://daffodil.apache.org/releases/3.4.0/ - https://GitHub.com/Apache/daffodil/ Best, Dave Sent from my iPhone On Feb 8, 2023, at 6:33 AM, PJ Fanning <fannin...@apache.org> wrote: Hi everyone, The release management guide [1] only mentions 'source releases'. Every Apache project that I am familiar with also does binary releases. For applications, this makes sense - having a zip/tgz file that you can download and extract - that you can then readily start the application using a shell script. For libs, I'm sure these binary releases can be useful too but I'm wondering if they are strictly required. Apache Pekko is a set of libraries as opposed to an application. Our build uses the sbt build tool and there isn't anything that I've come across that would produce something like the binary releases that other Apache projects release. This means we'd likely have to roll our own solution. In terms of prioritising work towards a v1.0.0 release, it's useful to know if we have items that could be de-prioritised. If we do need to create binary releases, are there any guidelines to follow - or do we just look at other Apache libs and use their binary releases as a guide? Regards, PJ [1] https://incubator.apache.org/guides/releasemanagement.html --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
