Hi Only source codes(tars) are treated as releases. So generally, you could only put the source tars as the vote releases.
Meanwhile, we should check the runtime dependencies about License compatibility, such as no Catalog X or commercial license dependencies in the runtime(especially not optional). Sheng Wu 吴晟 Twitter, wusheng1108 PJ Fanning <fannin...@apache.org> 于2023年2月8日周三 22:33写道： > > 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
