Hi PJ, Only source releases are required. Apache Kvrocks (Incubating) release 2.1.0 (the first Apache release) with sources only, although there's a following vote for Docker release due to user's requirement :)
You may refer to: https://lists.apache.org/thread/v63xyr8rw5o7h0flt3fx3mrn9vxsyskm https://lists.apache.org/thread/k744nbjf6vhvwkf8fb02t4l08rjxo7n7 I agree to release only sources helps the podling getting started with the new process, while please keep collecting users feedback :) Best, tison. 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 > >
