> I’m not sure if this is the case, but requiring docker to check the release may be a barrier to getting IPMC votes on your release.
Docker is required to make a correct and reproducible build of Pekko because Pekko requires multiple JDK's to be installed on the host systems, if this is not the case then some parts of Pekko will simply fail to work on some JDK's. While it is possible to inspect the final build without Docker, due to the fact that Pekko's build is reproducible the easiest way to confirm that the build is correct is by building Pekko via the docker image on a system and then confirming that the final jar's are the same as what the release manager is providing. While this may not be ideal, there also isn't any way around it at least if you want to correctly build Pekko. Pekko is not a trivial system to build and using Docker is far simpler than any alternative (at least that I know of). On Mon, May 22, 2023 at 2:53 AM Justin Mclean <[email protected]> wrote: > Hi, > > > The docker image is not a convenience package (this also foesnt make > sense > > since Pekko is a library), it's for creating a reproducible environment > for > > making a release. There are other ways to do this such as a VM image but > > docker is the least friction solution. > > I’m not sure if this is the case, but requiring docker to check the > release may be a barrier to getting IPMC votes on your release. > > Kind Regards, > Justin > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Matthew de Detrich *Aiven Deutschland GmbH* Immanuelkirchstraße 26, 10405 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen *m:* +491603708037 *w:* aiven.io *e:* [email protected]
