* It was pointed out that the health of the current contributors
isn't the
best (i.e. majority of work is being done by a few people). While
there
are
various factors behind this (such as work necessary for first
release
requires a lot of SBT knowledge, something that only a few people
can
provide right now) the bigger point to be made here is that its a
chicken
and egg situation ergo potential contributors are holding back
because
they
want confidence in the Pekko project before devoting their time
however
for
the project to be more successful we need more contributors for the
first
release.
This will sound stupid but a while ago I tried to figure out what I
can do
for Pekko, while I was expecting that somebody would tell me take
this
Issue and fix/implement it, the answer was choose an issue and work
with
it, I looked for three issue s, later to discover other people are
working
on those and then there was some private stuff and I could not be
that
active with contributing.
Now I have more time and am I looking ways to contribute, now is
there
anybody distributing issues or I still have to figure something
myself?
Thx for answers...
Gesendet: Montag, 08. Mai 2023 um 08:37 Uhr
Von: "Matthew Benedict de Detrich"
<[email protected]>
An: [email protected], [email protected]
Betreff: Plans for Pekko (core) 1.0.0 release
Johannes, PJ Fanning and myself had a discussion last week to
regarding
future plans regarding the Pekko 1.0.0 release, below are the
generate
points discussed on this topic
* We should focus on doing a Pekko release first for the core module
* In terms of actual technical work that needs to be done for a
future
first release, there doesn't appear to be a lot. The last main piece
of
work should be https://github.com/apache/incubator-pekko/pull/281.
There
is
also Scala 3.3 LTS but considering there is already an open PR for
RC4 on
this (see
https://github.com/apache/incubator-pekko/pull/270[https://github.com/apache/incubator-pekko/pull/270])
and RC4 is
expected to be the last RC before release, this shouldn't be a
concern. The
main thing to look at here is the docker image that Johannes made to
help
in creating a release (see
https://github.com/apache/incubator-pekko/pull/188[https://github.com/apache/incubator-pekko/pull/188]
)
* There are still open questions regarding legal questions (i.e.
headers)
but considering feedback is given on this by the community on a
voluntary
basis, its best to start off the release sooner rather than later to
trigger/solicit some proper feedback on this topic otherwise we would
be
waiting for an extortionate amount of time.
* Users of Akka looking to transition to Pekko have raised concerns
regarding the release schedule and how long it's taking. While it is
true
that the release is taking a long amount of time, it should be
pointed out
that this shouldn't be indicative of future releases. In other words,
a
large reason why the release is taking a long amount of time is that
we had
to deliberate, discuss, plan and actually develop the Apache release
process for the first time. Pekko is also a hard fork which is never
easy
and the current release process is reflecting that.
* It was pointed out that the health of the current contributors
isn't the
best (i.e. majority of work is being done by a few people). While
there are
various factors behind this (such as work necessary for first release
requires a lot of SBT knowledge, something that only a few people can
provide right now) the bigger point to be made here is that its a
chicken
and egg situation ergo potential contributors are holding back
because they
want confidence in the Pekko project before devoting their time
however for
the project to be more successful we need more contributors for the
first
release.
* We have decided to publish a MILESTONE in the snapshots repository
to
provide an indication that a release is coming soon. This will occur
after
https://github.com/apache/incubator-pekko/pull/270[https://github.com/apache/incubator-pekko/pull/270],
also because
https://github.com/apache/incubator-pekko/pull/270[https://github.com/apache/incubator-pekko/pull/270]
will require downstream
changes to every Pekko module (and its easier to refer to a MILESTONE
version rather than just git hashes).
* Documentation for the rest of the Pekko modules should be published
but
we shouldn't worry too much about getting the versioning of the docs
correct. Having something there is better than nothing, especially
considering that documentation is the first thing that users look
for.
Additional comments are welcome.
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
