The nightly publish job for pekko-projection ran successfully so the
snapshot artifact is ready to resolve (see
https://github.com/apache/incubator-pekko-projection/actions/runs/4537965655/jobs/7996388585
).
On Mon, Mar 27, 2023 at 11:11 PM Matthew Benedict de Detrich <
matthew.dedetr...@aiven.io>
An update on this, pekko-projections should broadly be ready. By this I
mean that the structural changes have been done, the project is set up to
publish to apache snapshots nightly (need to confirm on the first job run
which triggers in a few hours) and pekko-paradox has also been integrated.
Thi
I don't have a problem with this as well, but we should migrate
pekko-projections irregardless (actually I might have use for this where I
work so there is a selfish reason behind this). Since doing these
migrations is already second nature to me (from doing it so many times) I
am already opening u
I'm fine with removing (at least for now). In some way the guide is
one of the best high-level documentation for Akka that brings
everything together but on the other hand it's a somewhat ad-hoc
collection of documentation bits that seemed to fit nowhere else. In
many regards, it could make sense t
> My preference is to remove the links from the core Pekko docs [4] until
later. If we want to keep the links - do we just link to Akka Guide for now
or do we have the resources to migrate Pekko Projections and the Pekko
Platform Guide - and wait for that work to be done?
I will look into getting
Hi everyone,
With a view to trying to get the incubator-pekko repo ready for a v1.0.0
release, the docs that are in that repo link to docs and samples in many other
repos and if we don't prune some of these docs (at least temporarily), we will
be stuck having to migrate a much larger code base
