> A docker release is just a convenance to your users, it’s not an official
release.

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.

> Why wait? The longer you do so the harder it may be to grow a community
around this project. Making releases involves the community, they can
provide feedback and make contributions to improve the project.

Because since Pekko is a library that follows an ABI we can break users if
not careful and that is one of the most negative ways you can impact Pekko
users.

> Perhaps the project needs to consider a change to this approach?

This is an expectation for Scala/Java libraries so it's not really going to
change. It's not any different to Apache Commons also maintaining binary
compatibility (for example), it's just that it's harder for us since Pekko
is a cross Java/Scala library.

On Sun, 21 May 2023, 15:00 Justin Mclean, <[email protected]> wrote:

> Hi,
>
> > A lot of our complications for the release come from the fact that Pekko
> is
> > a library with very strict expectations for binary compatibility.(these
> > expectations are inherited from Akka).
>
> Perhaps the project needs to consider a change to this approach?
>
> > Thankfully as mentioned before the majority of the critical changes that
> > fulfil these expectations have already been done. Aside from further
> > documentation changes and getting the docker release working,
>
> A docker release is just a convenance to your users, it’s not an official
> release.
>
> > the major thing we are waiting for is Scala 3.3 LTS which is expected to
> come out
> > next week.
>
> Why wait? The longer you do so the harder it may be to grow a community
> around this project. Making releases involves the community, they can
> provide feedback and make contributions to improve the project.
>
> Kind Regards,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to