You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pekko.apache.org by PJ Fanning <fa...@apache.org> on 2024/03/18 20:44:37 UTC
[DISCUSS] Pekko 1.1.0-M1 release
Hi everyone,
I think we are in a good position to consider putting together a
1.1.0-M1-RC1 in the next week or so. I am aware that there are a
couple of changes still being worked on but I think if we stick to
what is the milestone [1], we should be able to decide whether we can
complete the remaining items or if we can delay them till the M2
release.
I have some basic release notes [2] and if anyone knows of any
existing changes that are missing, can you comment on the PR?
If anyone has any urgent changes, can you please discuss them on this
list instead of adding them to the milestone without discussion?
[1] https://github.com/apache/incubator-pekko/milestone/2
[2] https://github.com/apache/incubator-pekko/pull/1204
Thanks,
PJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: [DISCUSS] Pekko 1.1.0-M1 release
Posted by kerr <he...@gmail.com>.
Yes, I think we can do this.
何品
PJ Fanning <fa...@apache.org> 于2024年5月7日周二 21:30写道：
> Can we code freeze on main branch? I plan to create a 1.1.0-M1-RC1 tonight
> based on this latest commit.
>
>
> https://github.com/apache/pekko/commit/977e3091ceedfadace900197be29c4ca52015ece
>
>
>
> On 2024/05/07 04:28:56 kerr wrote:
> > Let's ship these
> > 何品
> >
> >
> > PJ Fanning <fa...@apache.org> 于2024年5月7日周二 08:16写道：
> >
> > > The tasks in the milestone as basically done. I need to update the
> release
> > > notes PR but that is not going to be merged until the release is
> approved.
> > >
> > > I have a couple of small PRs that are build related.
> > >
> > > Are there any objections to merging those?
> > >
> > > https://github.com/apache/pekko/pull/1312
> > > https://github.com/apache/pekko/pull/1313
> > >
> > > On 2024/04/27 12:28:51 kerr wrote:
> > > > I'm fine to have an M1 release with the current M1 milestone , I
> found
> > > time
> > > > to do a virtual thread support, but I will not have enough time to
> get it
> > > > ready for M1 I think, anyone could continue that work.
> > > > 何品
> > > >
> > > >
> > > > PJ Fanning <fa...@apache.org> 于2024年4月27日周六 04:21写道：
> > > >
> > > > > I think we are close again to making a release candidate.
> > > > >
> > > > > The remaining tasks:
> > > > > https://github.com/apache/pekko/milestone/2
> > > > >
> > > > > I can take on the 2 doc tasks. Can we get the other 2 items merged?
> > > > >
> > > > > Is there anything else?
> > > > >
> > > > > I can produce an RC next week if we get everything completed.
> > > > >
> > > > >
> > > > > On 2024/03/21 08:45:30 kerr wrote:
> > > > > > We may want to stick with some release cycle, eg a new minor
> version
> > > > > > release after every 6 months, etc, I still want to add something
> to
> > > M2, I
> > > > > > was expecting 1.1.0 to be released before the end of May.
> > > > > >
> > > > > >
> > > > > > 何品
> > > > > >
> > > > > >
> > > > > > PJ Fanning <fa...@apache.org> 于2024年3月21日周四 04:04写道：
> > > > > >
> > > > > > > I would like to add
> > > > > https://github.com/apache/incubator-pekko/pull/1211 -
> > > > > > > a forward fit of Pekko 1.0.3-M1 code. The response to that
> release
> > > has
> > > > > been
> > > > > > > underwhelming so I think we should include the changes in Pekko
> > > 1.1.
> > > > > We can
> > > > > > > remove the support for Akka clusters in a later release. We
> haven't
> > > > > made
> > > > > > > big breaking changes on Pekko 1.1 so users should be able to
> move
> > > to
> > > > > that
> > > > > > > from Akka without too much extra hassle. The support only
> kicks in
> > > if
> > > > > you
> > > > > > > enable certain configs.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 2024/03/20 07:25:51 Matthew de Detrich wrote:
> > > > > > > > So I would advocate for trying to avoid -M2 as much as we can
> > > which
> > > > > means
> > > > > > > > putting anything remaining into -M1, this is largely a
> result of
> > > the
> > > > > > > discussion
> > > > > > > > on pekko-grpc 1.1.0 release[1]. In other words in my view the
> > > most
> > > > > ideal
> > > > > > > > situatin would be to only have one milestone which implies a
> > > feature
> > > > > > > freeze
> > > > > > > > for -M1 but of course we can still solve bugs until the full
> > > release.
> > > > > > > >
> > > > > > > > For this reason I have removed
> > > > > > > > https://github.com/apache/incubator-pekko/pull/981
> > > > > > > > from the milestone with reasons explained in the PR.
> > > > > > > >
> > > > > > > > If we look at the -M2 milestone[2] we can see that there are
> > > quite a
> > > > > > > > few features there
> > > > > > > > but a fair amount of them seem on the horizon of being
> > > completed. The
> > > > > > > > only feature
> > > > > > > > request that realistically can fit in -M1 but is sitting in
> -M2
> > > that
> > > > > > > > we may unfortunately miss
> > > > > > > > is Source.generate/Source.iteratee methods[3]. I would like
> if
> > > that
> > > > > > > > could be included in
> > > > > > > > -M1 but I can see how that can be stretching it.
> > > > > > > >
> > > > > > > > 1:
> > > https://lists.apache.org/thread/rjygk60ho1mojk4rqsmvd2y4244d55lr
> > > > > > > > 2: https://github.com/apache/incubator-pekko/milestone/7
> > > > > > > > 3: https://github.com/apache/incubator-pekko/issues/1189
> > > > > > > >
> > > > > > > > On Mon, Mar 18, 2024 at 9:45 PM PJ Fanning <
> fanningpj@apache.org
> > > >
> > > > > wrote:
> > > > > > > > >
> > > > > > > > > Hi everyone,
> > > > > > > > >
> > > > > > > > > I think we are in a good position to consider putting
> together
> > > a
> > > > > > > > > 1.1.0-M1-RC1 in the next week or so. I am aware that there
> are
> > > a
> > > > > > > > > couple of changes still being worked on but I think if we
> > > stick to
> > > > > > > > > what is the milestone [1], we should be able to decide
> whether
> > > we
> > > > > can
> > > > > > > > > complete the remaining items or if we can delay them till
> the
> > > M2
> > > > > > > > > release.
> > > > > > > > >
> > > > > > > > > I have some basic release notes [2] and if anyone knows of
> any
> > > > > > > > > existing changes that are missing, can you comment on the
> PR?
> > > > > > > > >
> > > > > > > > > If anyone has any urgent changes, can you please discuss
> them
> > > on
> > > > > this
> > > > > > > > > list instead of adding them to the milestone without
> > > discussion?
> > > > > > > > >
> > > > > > > > > [1] https://github.com/apache/incubator-pekko/milestone/2
> > > > > > > > > [2] https://github.com/apache/incubator-pekko/pull/1204
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > PJ
> > > > > > > > >
> > > > > > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > >
> > > > > > > > Matthew de Detrich
> > > > > > > >
> > > > > > > > Aiven Deutschland GmbH
> > > > > > > >
> > > > > > > > Immanuelkirchstraße 26, 10405 Berlin
> > > > > > > >
> > > > > > > > Alexanderufer 3-7, 10117 Berlin
> > > > > > > >
> > > > > > > > Amtsgericht Charlottenburg, HRB 209739 B
> > > > > > > >
> > > > > > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > > > > > >
> > > > > > > > m: +491603708037
> > > > > > > >
> > > > > > > > w: aiven.io e: matthew.dedetrich@aiven.io
> > > > > > > >
> > > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > >
> > > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > For additional commands, e-mail: dev-help@pekko.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>
Re: [DISCUSS] Pekko 1.1.0-M1 release
Posted by PJ Fanning <fa...@apache.org>.
Can we code freeze on main branch? I plan to create a 1.1.0-M1-RC1 tonight based on this latest commit.
https://github.com/apache/pekko/commit/977e3091ceedfadace900197be29c4ca52015ece
On 2024/05/07 04:28:56 kerr wrote:
> Let's ship these
> 何品
>
>
> PJ Fanning <fa...@apache.org> 于2024年5月7日周二 08:16写道：
>
> > The tasks in the milestone as basically done. I need to update the release
> > notes PR but that is not going to be merged until the release is approved.
> >
> > I have a couple of small PRs that are build related.
> >
> > Are there any objections to merging those?
> >
> > https://github.com/apache/pekko/pull/1312
> > https://github.com/apache/pekko/pull/1313
> >
> > On 2024/04/27 12:28:51 kerr wrote:
> > > I'm fine to have an M1 release with the current M1 milestone , I found
> > time
> > > to do a virtual thread support, but I will not have enough time to get it
> > > ready for M1 I think, anyone could continue that work.
> > > 何品
> > >
> > >
> > > PJ Fanning <fa...@apache.org> 于2024年4月27日周六 04:21写道：
> > >
> > > > I think we are close again to making a release candidate.
> > > >
> > > > The remaining tasks:
> > > > https://github.com/apache/pekko/milestone/2
> > > >
> > > > I can take on the 2 doc tasks. Can we get the other 2 items merged?
> > > >
> > > > Is there anything else?
> > > >
> > > > I can produce an RC next week if we get everything completed.
> > > >
> > > >
> > > > On 2024/03/21 08:45:30 kerr wrote:
> > > > > We may want to stick with some release cycle, eg a new minor version
> > > > > release after every 6 months, etc, I still want to add something to
> > M2, I
> > > > > was expecting 1.1.0 to be released before the end of May.
> > > > >
> > > > >
> > > > > 何品
> > > > >
> > > > >
> > > > > PJ Fanning <fa...@apache.org> 于2024年3月21日周四 04:04写道：
> > > > >
> > > > > > I would like to add
> > > > https://github.com/apache/incubator-pekko/pull/1211 -
> > > > > > a forward fit of Pekko 1.0.3-M1 code. The response to that release
> > has
> > > > been
> > > > > > underwhelming so I think we should include the changes in Pekko
> > 1.1.
> > > > We can
> > > > > > remove the support for Akka clusters in a later release. We haven't
> > > > made
> > > > > > big breaking changes on Pekko 1.1 so users should be able to move
> > to
> > > > that
> > > > > > from Akka without too much extra hassle. The support only kicks in
> > if
> > > > you
> > > > > > enable certain configs.
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 2024/03/20 07:25:51 Matthew de Detrich wrote:
> > > > > > > So I would advocate for trying to avoid -M2 as much as we can
> > which
> > > > means
> > > > > > > putting anything remaining into -M1, this is largely a result of
> > the
> > > > > > discussion
> > > > > > > on pekko-grpc 1.1.0 release[1]. In other words in my view the
> > most
> > > > ideal
> > > > > > > situatin would be to only have one milestone which implies a
> > feature
> > > > > > freeze
> > > > > > > for -M1 but of course we can still solve bugs until the full
> > release.
> > > > > > >
> > > > > > > For this reason I have removed
> > > > > > > https://github.com/apache/incubator-pekko/pull/981
> > > > > > > from the milestone with reasons explained in the PR.
> > > > > > >
> > > > > > > If we look at the -M2 milestone[2] we can see that there are
> > quite a
> > > > > > > few features there
> > > > > > > but a fair amount of them seem on the horizon of being
> > completed. The
> > > > > > > only feature
> > > > > > > request that realistically can fit in -M1 but is sitting in -M2
> > that
> > > > > > > we may unfortunately miss
> > > > > > > is Source.generate/Source.iteratee methods[3]. I would like if
> > that
> > > > > > > could be included in
> > > > > > > -M1 but I can see how that can be stretching it.
> > > > > > >
> > > > > > > 1:
> > https://lists.apache.org/thread/rjygk60ho1mojk4rqsmvd2y4244d55lr
> > > > > > > 2: https://github.com/apache/incubator-pekko/milestone/7
> > > > > > > 3: https://github.com/apache/incubator-pekko/issues/1189
> > > > > > >
> > > > > > > On Mon, Mar 18, 2024 at 9:45 PM PJ Fanning <fanningpj@apache.org
> > >
> > > > wrote:
> > > > > > > >
> > > > > > > > Hi everyone,
> > > > > > > >
> > > > > > > > I think we are in a good position to consider putting together
> > a
> > > > > > > > 1.1.0-M1-RC1 in the next week or so. I am aware that there are
> > a
> > > > > > > > couple of changes still being worked on but I think if we
> > stick to
> > > > > > > > what is the milestone [1], we should be able to decide whether
> > we
> > > > can
> > > > > > > > complete the remaining items or if we can delay them till the
> > M2
> > > > > > > > release.
> > > > > > > >
> > > > > > > > I have some basic release notes [2] and if anyone knows of any
> > > > > > > > existing changes that are missing, can you comment on the PR?
> > > > > > > >
> > > > > > > > If anyone has any urgent changes, can you please discuss them
> > on
> > > > this
> > > > > > > > list instead of adding them to the milestone without
> > discussion?
> > > > > > > >
> > > > > > > > [1] https://github.com/apache/incubator-pekko/milestone/2
> > > > > > > > [2] https://github.com/apache/incubator-pekko/pull/1204
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > PJ
> > > > > > > >
> > > > > > > >
> > > > ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > Matthew de Detrich
> > > > > > >
> > > > > > > Aiven Deutschland GmbH
> > > > > > >
> > > > > > > Immanuelkirchstraße 26, 10405 Berlin
> > > > > > >
> > > > > > > Alexanderufer 3-7, 10117 Berlin
> > > > > > >
> > > > > > > Amtsgericht Charlottenburg, HRB 209739 B
> > > > > > >
> > > > > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > > > > >
> > > > > > > m: +491603708037
> > > > > > >
> > > > > > > w: aiven.io e: matthew.dedetrich@aiven.io
> > > > > > >
> > > > > > >
> > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > >
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > For additional commands, e-mail: dev-help@pekko.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: [DISCUSS] Pekko 1.1.0-M1 release
Posted by kerr <he...@gmail.com>.
Let's ship these
何品
PJ Fanning <fa...@apache.org> 于2024年5月7日周二 08:16写道：
> The tasks in the milestone as basically done. I need to update the release
> notes PR but that is not going to be merged until the release is approved.
>
> I have a couple of small PRs that are build related.
>
> Are there any objections to merging those?
>
> https://github.com/apache/pekko/pull/1312
> https://github.com/apache/pekko/pull/1313
>
> On 2024/04/27 12:28:51 kerr wrote:
> > I'm fine to have an M1 release with the current M1 milestone , I found
> time
> > to do a virtual thread support, but I will not have enough time to get it
> > ready for M1 I think, anyone could continue that work.
> > 何品
> >
> >
> > PJ Fanning <fa...@apache.org> 于2024年4月27日周六 04:21写道：
> >
> > > I think we are close again to making a release candidate.
> > >
> > > The remaining tasks:
> > > https://github.com/apache/pekko/milestone/2
> > >
> > > I can take on the 2 doc tasks. Can we get the other 2 items merged?
> > >
> > > Is there anything else?
> > >
> > > I can produce an RC next week if we get everything completed.
> > >
> > >
> > > On 2024/03/21 08:45:30 kerr wrote:
> > > > We may want to stick with some release cycle, eg a new minor version
> > > > release after every 6 months, etc, I still want to add something to
> M2, I
> > > > was expecting 1.1.0 to be released before the end of May.
> > > >
> > > >
> > > > 何品
> > > >
> > > >
> > > > PJ Fanning <fa...@apache.org> 于2024年3月21日周四 04:04写道：
> > > >
> > > > > I would like to add
> > > https://github.com/apache/incubator-pekko/pull/1211 -
> > > > > a forward fit of Pekko 1.0.3-M1 code. The response to that release
> has
> > > been
> > > > > underwhelming so I think we should include the changes in Pekko
> 1.1.
> > > We can
> > > > > remove the support for Akka clusters in a later release. We haven't
> > > made
> > > > > big breaking changes on Pekko 1.1 so users should be able to move
> to
> > > that
> > > > > from Akka without too much extra hassle. The support only kicks in
> if
> > > you
> > > > > enable certain configs.
> > > > >
> > > > >
> > > > >
> > > > > On 2024/03/20 07:25:51 Matthew de Detrich wrote:
> > > > > > So I would advocate for trying to avoid -M2 as much as we can
> which
> > > means
> > > > > > putting anything remaining into -M1, this is largely a result of
> the
> > > > > discussion
> > > > > > on pekko-grpc 1.1.0 release[1]. In other words in my view the
> most
> > > ideal
> > > > > > situatin would be to only have one milestone which implies a
> feature
> > > > > freeze
> > > > > > for -M1 but of course we can still solve bugs until the full
> release.
> > > > > >
> > > > > > For this reason I have removed
> > > > > > https://github.com/apache/incubator-pekko/pull/981
> > > > > > from the milestone with reasons explained in the PR.
> > > > > >
> > > > > > If we look at the -M2 milestone[2] we can see that there are
> quite a
> > > > > > few features there
> > > > > > but a fair amount of them seem on the horizon of being
> completed. The
> > > > > > only feature
> > > > > > request that realistically can fit in -M1 but is sitting in -M2
> that
> > > > > > we may unfortunately miss
> > > > > > is Source.generate/Source.iteratee methods[3]. I would like if
> that
> > > > > > could be included in
> > > > > > -M1 but I can see how that can be stretching it.
> > > > > >
> > > > > > 1:
> https://lists.apache.org/thread/rjygk60ho1mojk4rqsmvd2y4244d55lr
> > > > > > 2: https://github.com/apache/incubator-pekko/milestone/7
> > > > > > 3: https://github.com/apache/incubator-pekko/issues/1189
> > > > > >
> > > > > > On Mon, Mar 18, 2024 at 9:45 PM PJ Fanning <fanningpj@apache.org
> >
> > > wrote:
> > > > > > >
> > > > > > > Hi everyone,
> > > > > > >
> > > > > > > I think we are in a good position to consider putting together
> a
> > > > > > > 1.1.0-M1-RC1 in the next week or so. I am aware that there are
> a
> > > > > > > couple of changes still being worked on but I think if we
> stick to
> > > > > > > what is the milestone [1], we should be able to decide whether
> we
> > > can
> > > > > > > complete the remaining items or if we can delay them till the
> M2
> > > > > > > release.
> > > > > > >
> > > > > > > I have some basic release notes [2] and if anyone knows of any
> > > > > > > existing changes that are missing, can you comment on the PR?
> > > > > > >
> > > > > > > If anyone has any urgent changes, can you please discuss them
> on
> > > this
> > > > > > > list instead of adding them to the milestone without
> discussion?
> > > > > > >
> > > > > > > [1] https://github.com/apache/incubator-pekko/milestone/2
> > > > > > > [2] https://github.com/apache/incubator-pekko/pull/1204
> > > > > > >
> > > > > > > Thanks,
> > > > > > > PJ
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Matthew de Detrich
> > > > > >
> > > > > > Aiven Deutschland GmbH
> > > > > >
> > > > > > Immanuelkirchstraße 26, 10405 Berlin
> > > > > >
> > > > > > Alexanderufer 3-7, 10117 Berlin
> > > > > >
> > > > > > Amtsgericht Charlottenburg, HRB 209739 B
> > > > > >
> > > > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > > > >
> > > > > > m: +491603708037
> > > > > >
> > > > > > w: aiven.io e: matthew.dedetrich@aiven.io
> > > > > >
> > > > > >
> ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > >
> > > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > For additional commands, e-mail: dev-help@pekko.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>
Re: [DISCUSS] Pekko 1.1.0-M1 release
Posted by PJ Fanning <fa...@apache.org>.
The tasks in the milestone as basically done. I need to update the release notes PR but that is not going to be merged until the release is approved.
I have a couple of small PRs that are build related.
Are there any objections to merging those?
https://github.com/apache/pekko/pull/1312
https://github.com/apache/pekko/pull/1313
On 2024/04/27 12:28:51 kerr wrote:
> I'm fine to have an M1 release with the current M1 milestone , I found time
> to do a virtual thread support, but I will not have enough time to get it
> ready for M1 I think, anyone could continue that work.
> 何品
>
>
> PJ Fanning <fa...@apache.org> 于2024年4月27日周六 04:21写道：
>
> > I think we are close again to making a release candidate.
> >
> > The remaining tasks:
> > https://github.com/apache/pekko/milestone/2
> >
> > I can take on the 2 doc tasks. Can we get the other 2 items merged?
> >
> > Is there anything else?
> >
> > I can produce an RC next week if we get everything completed.
> >
> >
> > On 2024/03/21 08:45:30 kerr wrote:
> > > We may want to stick with some release cycle, eg a new minor version
> > > release after every 6 months, etc, I still want to add something to M2, I
> > > was expecting 1.1.0 to be released before the end of May.
> > >
> > >
> > > 何品
> > >
> > >
> > > PJ Fanning <fa...@apache.org> 于2024年3月21日周四 04:04写道：
> > >
> > > > I would like to add
> > https://github.com/apache/incubator-pekko/pull/1211 -
> > > > a forward fit of Pekko 1.0.3-M1 code. The response to that release has
> > been
> > > > underwhelming so I think we should include the changes in Pekko 1.1.
> > We can
> > > > remove the support for Akka clusters in a later release. We haven't
> > made
> > > > big breaking changes on Pekko 1.1 so users should be able to move to
> > that
> > > > from Akka without too much extra hassle. The support only kicks in if
> > you
> > > > enable certain configs.
> > > >
> > > >
> > > >
> > > > On 2024/03/20 07:25:51 Matthew de Detrich wrote:
> > > > > So I would advocate for trying to avoid -M2 as much as we can which
> > means
> > > > > putting anything remaining into -M1, this is largely a result of the
> > > > discussion
> > > > > on pekko-grpc 1.1.0 release[1]. In other words in my view the most
> > ideal
> > > > > situatin would be to only have one milestone which implies a feature
> > > > freeze
> > > > > for -M1 but of course we can still solve bugs until the full release.
> > > > >
> > > > > For this reason I have removed
> > > > > https://github.com/apache/incubator-pekko/pull/981
> > > > > from the milestone with reasons explained in the PR.
> > > > >
> > > > > If we look at the -M2 milestone[2] we can see that there are quite a
> > > > > few features there
> > > > > but a fair amount of them seem on the horizon of being completed. The
> > > > > only feature
> > > > > request that realistically can fit in -M1 but is sitting in -M2 that
> > > > > we may unfortunately miss
> > > > > is Source.generate/Source.iteratee methods[3]. I would like if that
> > > > > could be included in
> > > > > -M1 but I can see how that can be stretching it.
> > > > >
> > > > > 1: https://lists.apache.org/thread/rjygk60ho1mojk4rqsmvd2y4244d55lr
> > > > > 2: https://github.com/apache/incubator-pekko/milestone/7
> > > > > 3: https://github.com/apache/incubator-pekko/issues/1189
> > > > >
> > > > > On Mon, Mar 18, 2024 at 9:45 PM PJ Fanning <fa...@apache.org>
> > wrote:
> > > > > >
> > > > > > Hi everyone,
> > > > > >
> > > > > > I think we are in a good position to consider putting together a
> > > > > > 1.1.0-M1-RC1 in the next week or so. I am aware that there are a
> > > > > > couple of changes still being worked on but I think if we stick to
> > > > > > what is the milestone [1], we should be able to decide whether we
> > can
> > > > > > complete the remaining items or if we can delay them till the M2
> > > > > > release.
> > > > > >
> > > > > > I have some basic release notes [2] and if anyone knows of any
> > > > > > existing changes that are missing, can you comment on the PR?
> > > > > >
> > > > > > If anyone has any urgent changes, can you please discuss them on
> > this
> > > > > > list instead of adding them to the milestone without discussion?
> > > > > >
> > > > > > [1] https://github.com/apache/incubator-pekko/milestone/2
> > > > > > [2] https://github.com/apache/incubator-pekko/pull/1204
> > > > > >
> > > > > > Thanks,
> > > > > > PJ
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Matthew de Detrich
> > > > >
> > > > > Aiven Deutschland GmbH
> > > > >
> > > > > Immanuelkirchstraße 26, 10405 Berlin
> > > > >
> > > > > Alexanderufer 3-7, 10117 Berlin
> > > > >
> > > > > Amtsgericht Charlottenburg, HRB 209739 B
> > > > >
> > > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > > >
> > > > > m: +491603708037
> > > > >
> > > > > w: aiven.io e: matthew.dedetrich@aiven.io
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > >
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > For additional commands, e-mail: dev-help@pekko.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: [DISCUSS] Pekko 1.1.0-M1 release
Posted by kerr <he...@gmail.com>.
I'm fine to have an M1 release with the current M1 milestone , I found time
to do a virtual thread support, but I will not have enough time to get it
ready for M1 I think, anyone could continue that work.
何品
PJ Fanning <fa...@apache.org> 于2024年4月27日周六 04:21写道：
> I think we are close again to making a release candidate.
>
> The remaining tasks:
> https://github.com/apache/pekko/milestone/2
>
> I can take on the 2 doc tasks. Can we get the other 2 items merged?
>
> Is there anything else?
>
> I can produce an RC next week if we get everything completed.
>
>
> On 2024/03/21 08:45:30 kerr wrote:
> > We may want to stick with some release cycle, eg a new minor version
> > release after every 6 months, etc, I still want to add something to M2, I
> > was expecting 1.1.0 to be released before the end of May.
> >
> >
> > 何品
> >
> >
> > PJ Fanning <fa...@apache.org> 于2024年3月21日周四 04:04写道：
> >
> > > I would like to add
> https://github.com/apache/incubator-pekko/pull/1211 -
> > > a forward fit of Pekko 1.0.3-M1 code. The response to that release has
> been
> > > underwhelming so I think we should include the changes in Pekko 1.1.
> We can
> > > remove the support for Akka clusters in a later release. We haven't
> made
> > > big breaking changes on Pekko 1.1 so users should be able to move to
> that
> > > from Akka without too much extra hassle. The support only kicks in if
> you
> > > enable certain configs.
> > >
> > >
> > >
> > > On 2024/03/20 07:25:51 Matthew de Detrich wrote:
> > > > So I would advocate for trying to avoid -M2 as much as we can which
> means
> > > > putting anything remaining into -M1, this is largely a result of the
> > > discussion
> > > > on pekko-grpc 1.1.0 release[1]. In other words in my view the most
> ideal
> > > > situatin would be to only have one milestone which implies a feature
> > > freeze
> > > > for -M1 but of course we can still solve bugs until the full release.
> > > >
> > > > For this reason I have removed
> > > > https://github.com/apache/incubator-pekko/pull/981
> > > > from the milestone with reasons explained in the PR.
> > > >
> > > > If we look at the -M2 milestone[2] we can see that there are quite a
> > > > few features there
> > > > but a fair amount of them seem on the horizon of being completed. The
> > > > only feature
> > > > request that realistically can fit in -M1 but is sitting in -M2 that
> > > > we may unfortunately miss
> > > > is Source.generate/Source.iteratee methods[3]. I would like if that
> > > > could be included in
> > > > -M1 but I can see how that can be stretching it.
> > > >
> > > > 1: https://lists.apache.org/thread/rjygk60ho1mojk4rqsmvd2y4244d55lr
> > > > 2: https://github.com/apache/incubator-pekko/milestone/7
> > > > 3: https://github.com/apache/incubator-pekko/issues/1189
> > > >
> > > > On Mon, Mar 18, 2024 at 9:45 PM PJ Fanning <fa...@apache.org>
> wrote:
> > > > >
> > > > > Hi everyone,
> > > > >
> > > > > I think we are in a good position to consider putting together a
> > > > > 1.1.0-M1-RC1 in the next week or so. I am aware that there are a
> > > > > couple of changes still being worked on but I think if we stick to
> > > > > what is the milestone [1], we should be able to decide whether we
> can
> > > > > complete the remaining items or if we can delay them till the M2
> > > > > release.
> > > > >
> > > > > I have some basic release notes [2] and if anyone knows of any
> > > > > existing changes that are missing, can you comment on the PR?
> > > > >
> > > > > If anyone has any urgent changes, can you please discuss them on
> this
> > > > > list instead of adding them to the milestone without discussion?
> > > > >
> > > > > [1] https://github.com/apache/incubator-pekko/milestone/2
> > > > > [2] https://github.com/apache/incubator-pekko/pull/1204
> > > > >
> > > > > Thanks,
> > > > > PJ
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Matthew de Detrich
> > > >
> > > > Aiven Deutschland GmbH
> > > >
> > > > Immanuelkirchstraße 26, 10405 Berlin
> > > >
> > > > Alexanderufer 3-7, 10117 Berlin
> > > >
> > > > Amtsgericht Charlottenburg, HRB 209739 B
> > > >
> > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > >
> > > > m: +491603708037
> > > >
> > > > w: aiven.io e: matthew.dedetrich@aiven.io
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > For additional commands, e-mail: dev-help@pekko.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>
Re: [DISCUSS] Pekko 1.1.0-M1 release
Posted by PJ Fanning <fa...@apache.org>.
I think we are close again to making a release candidate.
The remaining tasks:
https://github.com/apache/pekko/milestone/2
I can take on the 2 doc tasks. Can we get the other 2 items merged?
Is there anything else?
I can produce an RC next week if we get everything completed.
On 2024/03/21 08:45:30 kerr wrote:
> We may want to stick with some release cycle, eg a new minor version
> release after every 6 months, etc, I still want to add something to M2, I
> was expecting 1.1.0 to be released before the end of May.
>
>
> 何品
>
>
> PJ Fanning <fa...@apache.org> 于2024年3月21日周四 04:04写道：
>
> > I would like to add https://github.com/apache/incubator-pekko/pull/1211 -
> > a forward fit of Pekko 1.0.3-M1 code. The response to that release has been
> > underwhelming so I think we should include the changes in Pekko 1.1. We can
> > remove the support for Akka clusters in a later release. We haven't made
> > big breaking changes on Pekko 1.1 so users should be able to move to that
> > from Akka without too much extra hassle. The support only kicks in if you
> > enable certain configs.
> >
> >
> >
> > On 2024/03/20 07:25:51 Matthew de Detrich wrote:
> > > So I would advocate for trying to avoid -M2 as much as we can which means
> > > putting anything remaining into -M1, this is largely a result of the
> > discussion
> > > on pekko-grpc 1.1.0 release[1]. In other words in my view the most ideal
> > > situatin would be to only have one milestone which implies a feature
> > freeze
> > > for -M1 but of course we can still solve bugs until the full release.
> > >
> > > For this reason I have removed
> > > https://github.com/apache/incubator-pekko/pull/981
> > > from the milestone with reasons explained in the PR.
> > >
> > > If we look at the -M2 milestone[2] we can see that there are quite a
> > > few features there
> > > but a fair amount of them seem on the horizon of being completed. The
> > > only feature
> > > request that realistically can fit in -M1 but is sitting in -M2 that
> > > we may unfortunately miss
> > > is Source.generate/Source.iteratee methods[3]. I would like if that
> > > could be included in
> > > -M1 but I can see how that can be stretching it.
> > >
> > > 1: https://lists.apache.org/thread/rjygk60ho1mojk4rqsmvd2y4244d55lr
> > > 2: https://github.com/apache/incubator-pekko/milestone/7
> > > 3: https://github.com/apache/incubator-pekko/issues/1189
> > >
> > > On Mon, Mar 18, 2024 at 9:45 PM PJ Fanning <fa...@apache.org> wrote:
> > > >
> > > > Hi everyone,
> > > >
> > > > I think we are in a good position to consider putting together a
> > > > 1.1.0-M1-RC1 in the next week or so. I am aware that there are a
> > > > couple of changes still being worked on but I think if we stick to
> > > > what is the milestone [1], we should be able to decide whether we can
> > > > complete the remaining items or if we can delay them till the M2
> > > > release.
> > > >
> > > > I have some basic release notes [2] and if anyone knows of any
> > > > existing changes that are missing, can you comment on the PR?
> > > >
> > > > If anyone has any urgent changes, can you please discuss them on this
> > > > list instead of adding them to the milestone without discussion?
> > > >
> > > > [1] https://github.com/apache/incubator-pekko/milestone/2
> > > > [2] https://github.com/apache/incubator-pekko/pull/1204
> > > >
> > > > Thanks,
> > > > PJ
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > >
> > >
> > >
> > > --
> > >
> > > Matthew de Detrich
> > >
> > > Aiven Deutschland GmbH
> > >
> > > Immanuelkirchstraße 26, 10405 Berlin
> > >
> > > Alexanderufer 3-7, 10117 Berlin
> > >
> > > Amtsgericht Charlottenburg, HRB 209739 B
> > >
> > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > >
> > > m: +491603708037
> > >
> > > w: aiven.io e: matthew.dedetrich@aiven.io
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > For additional commands, e-mail: dev-help@pekko.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > For additional commands, e-mail: dev-help@pekko.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: [DISCUSS] Pekko 1.1.0-M1 release
Posted by kerr <he...@gmail.com>.
We may want to stick with some release cycle, eg a new minor version
release after every 6 months, etc, I still want to add something to M2, I
was expecting 1.1.0 to be released before the end of May.
何品
PJ Fanning <fa...@apache.org> 于2024年3月21日周四 04:04写道：
> I would like to add https://github.com/apache/incubator-pekko/pull/1211 -
> a forward fit of Pekko 1.0.3-M1 code. The response to that release has been
> underwhelming so I think we should include the changes in Pekko 1.1. We can
> remove the support for Akka clusters in a later release. We haven't made
> big breaking changes on Pekko 1.1 so users should be able to move to that
> from Akka without too much extra hassle. The support only kicks in if you
> enable certain configs.
>
>
>
> On 2024/03/20 07:25:51 Matthew de Detrich wrote:
> > So I would advocate for trying to avoid -M2 as much as we can which means
> > putting anything remaining into -M1, this is largely a result of the
> discussion
> > on pekko-grpc 1.1.0 release[1]. In other words in my view the most ideal
> > situatin would be to only have one milestone which implies a feature
> freeze
> > for -M1 but of course we can still solve bugs until the full release.
> >
> > For this reason I have removed
> > https://github.com/apache/incubator-pekko/pull/981
> > from the milestone with reasons explained in the PR.
> >
> > If we look at the -M2 milestone[2] we can see that there are quite a
> > few features there
> > but a fair amount of them seem on the horizon of being completed. The
> > only feature
> > request that realistically can fit in -M1 but is sitting in -M2 that
> > we may unfortunately miss
> > is Source.generate/Source.iteratee methods[3]. I would like if that
> > could be included in
> > -M1 but I can see how that can be stretching it.
> >
> > 1: https://lists.apache.org/thread/rjygk60ho1mojk4rqsmvd2y4244d55lr
> > 2: https://github.com/apache/incubator-pekko/milestone/7
> > 3: https://github.com/apache/incubator-pekko/issues/1189
> >
> > On Mon, Mar 18, 2024 at 9:45 PM PJ Fanning <fa...@apache.org> wrote:
> > >
> > > Hi everyone,
> > >
> > > I think we are in a good position to consider putting together a
> > > 1.1.0-M1-RC1 in the next week or so. I am aware that there are a
> > > couple of changes still being worked on but I think if we stick to
> > > what is the milestone [1], we should be able to decide whether we can
> > > complete the remaining items or if we can delay them till the M2
> > > release.
> > >
> > > I have some basic release notes [2] and if anyone knows of any
> > > existing changes that are missing, can you comment on the PR?
> > >
> > > If anyone has any urgent changes, can you please discuss them on this
> > > list instead of adding them to the milestone without discussion?
> > >
> > > [1] https://github.com/apache/incubator-pekko/milestone/2
> > > [2] https://github.com/apache/incubator-pekko/pull/1204
> > >
> > > Thanks,
> > > PJ
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > For additional commands, e-mail: dev-help@pekko.apache.org
> > >
> >
> >
> > --
> >
> > Matthew de Detrich
> >
> > Aiven Deutschland GmbH
> >
> > Immanuelkirchstraße 26, 10405 Berlin
> >
> > Alexanderufer 3-7, 10117 Berlin
> >
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >
> > m: +491603708037
> >
> > w: aiven.io e: matthew.dedetrich@aiven.io
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > For additional commands, e-mail: dev-help@pekko.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>
Re: [DISCUSS] Pekko 1.1.0-M1 release
Posted by PJ Fanning <fa...@apache.org>.
I would like to add https://github.com/apache/incubator-pekko/pull/1211 - a forward fit of Pekko 1.0.3-M1 code. The response to that release has been underwhelming so I think we should include the changes in Pekko 1.1. We can remove the support for Akka clusters in a later release. We haven't made big breaking changes on Pekko 1.1 so users should be able to move to that from Akka without too much extra hassle. The support only kicks in if you enable certain configs.
On 2024/03/20 07:25:51 Matthew de Detrich wrote:
> So I would advocate for trying to avoid -M2 as much as we can which means
> putting anything remaining into -M1, this is largely a result of the discussion
> on pekko-grpc 1.1.0 release[1]. In other words in my view the most ideal
> situatin would be to only have one milestone which implies a feature freeze
> for -M1 but of course we can still solve bugs until the full release.
>
> For this reason I have removed
> https://github.com/apache/incubator-pekko/pull/981
> from the milestone with reasons explained in the PR.
>
> If we look at the -M2 milestone[2] we can see that there are quite a
> few features there
> but a fair amount of them seem on the horizon of being completed. The
> only feature
> request that realistically can fit in -M1 but is sitting in -M2 that
> we may unfortunately miss
> is Source.generate/Source.iteratee methods[3]. I would like if that
> could be included in
> -M1 but I can see how that can be stretching it.
>
> 1: https://lists.apache.org/thread/rjygk60ho1mojk4rqsmvd2y4244d55lr
> 2: https://github.com/apache/incubator-pekko/milestone/7
> 3: https://github.com/apache/incubator-pekko/issues/1189
>
> On Mon, Mar 18, 2024 at 9:45 PM PJ Fanning <fa...@apache.org> wrote:
> >
> > Hi everyone,
> >
> > I think we are in a good position to consider putting together a
> > 1.1.0-M1-RC1 in the next week or so. I am aware that there are a
> > couple of changes still being worked on but I think if we stick to
> > what is the milestone [1], we should be able to decide whether we can
> > complete the remaining items or if we can delay them till the M2
> > release.
> >
> > I have some basic release notes [2] and if anyone knows of any
> > existing changes that are missing, can you comment on the PR?
> >
> > If anyone has any urgent changes, can you please discuss them on this
> > list instead of adding them to the milestone without discussion?
> >
> > [1] https://github.com/apache/incubator-pekko/milestone/2
> > [2] https://github.com/apache/incubator-pekko/pull/1204
> >
> > Thanks,
> > PJ
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > For additional commands, e-mail: dev-help@pekko.apache.org
> >
>
>
> --
>
> Matthew de Detrich
>
> Aiven Deutschland GmbH
>
> Immanuelkirchstraße 26, 10405 Berlin
>
> Alexanderufer 3-7, 10117 Berlin
>
> Amtsgericht Charlottenburg, HRB 209739 B
>
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>
> m: +491603708037
>
> w: aiven.io e: matthew.dedetrich@aiven.io
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: [DISCUSS] Pekko 1.1.0-M1 release
Posted by Matthew de Detrich <ma...@aiven.io.INVALID>.
So I would advocate for trying to avoid -M2 as much as we can which means
putting anything remaining into -M1, this is largely a result of the discussion
on pekko-grpc 1.1.0 release[1]. In other words in my view the most ideal
situatin would be to only have one milestone which implies a feature freeze
for -M1 but of course we can still solve bugs until the full release.
For this reason I have removed
https://github.com/apache/incubator-pekko/pull/981
from the milestone with reasons explained in the PR.
If we look at the -M2 milestone[2] we can see that there are quite a
few features there
but a fair amount of them seem on the horizon of being completed. The
only feature
request that realistically can fit in -M1 but is sitting in -M2 that
we may unfortunately miss
is Source.generate/Source.iteratee methods[3]. I would like if that
could be included in
-M1 but I can see how that can be stretching it.
1: https://lists.apache.org/thread/rjygk60ho1mojk4rqsmvd2y4244d55lr
2: https://github.com/apache/incubator-pekko/milestone/7
3: https://github.com/apache/incubator-pekko/issues/1189
On Mon, Mar 18, 2024 at 9:45 PM PJ Fanning <fa...@apache.org> wrote:
>
> Hi everyone,
>
> I think we are in a good position to consider putting together a
> 1.1.0-M1-RC1 in the next week or so. I am aware that there are a
> couple of changes still being worked on but I think if we stick to
> what is the milestone [1], we should be able to decide whether we can
> complete the remaining items or if we can delay them till the M2
> release.
>
> I have some basic release notes [2] and if anyone knows of any
> existing changes that are missing, can you comment on the PR?
>
> If anyone has any urgent changes, can you please discuss them on this
> list instead of adding them to the milestone without discussion?
>
> [1] https://github.com/apache/incubator-pekko/milestone/2
> [2] https://github.com/apache/incubator-pekko/pull/1204
>
> Thanks,
> PJ
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
--
Matthew de Detrich
Aiven Deutschland GmbH
Immanuelkirchstraße 26, 10405 Berlin
Alexanderufer 3-7, 10117 Berlin
Amtsgericht Charlottenburg, HRB 209739 B
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
m: +491603708037
w: aiven.io e: matthew.dedetrich@aiven.io
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org