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 2025/01/11 12:28:40 UTC

[VOTE] Release Apache Pekko Connectors 1.1.0-RC1

Hello Pekko Community,

This is a call for a vote to release Apache Pekko Connectors 1.1.0-RC1.

The discussion thread:

https://lists.apache.org/thread/lnjdb2xf38jxsnox1k51zw7ny3f97ot9

The release candidate:

https://dist.apache.org/repos/dist/dev/pekko/CONNECTORS-1.1.0-RC1/

This release has been signed with a PGP key available here:

https://downloads.apache.org/pekko/KEYS

Release Notes:

https://github.com/apache/pekko-connectors/pull/861/files

Git tag for the release:

https://github.com/apache/pekko-connectors/tree/v1.1.0-RC1
Git commit ID: 63f1cefac096f21a93b8ae64a395d4c6bce43caa

Please download, verify, and test.

I have also staged jars in the Apache Nexus Repository. These were built
with the same code as appears in this Source Release Candidate.
I would appreciate if users could test with these too.
If anyone finds any serious problems with these jars, please also notify us
on this thread.

https://repository.apache.org/content/groups/staging/org/apache/pekko/

For sbt 1.9.4 or greater you can add this resolver

resolvers += Resolver.ApacheMavenStagingRepo

Otherwise for older versions of sbt

resolvers += "Apache Pekko Staging" at "
https://repository.apache.org/content/groups/staging"


The VOTE will pass if we have more positive votes than negative votes
and there must be a minimum of 3 approvals from Pekko PMC members.
Anyone voting in favour of the release, could you please provide a list of
the checks you have done?
The vote will be left open for at least 72hrs.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

To learn more about Apache Pekko, please see https://pekko.apache.org/

Checklist for reference:

[ ] Download links are valid.
[ ] Checksums and signatures.
[ ] LICENSE/NOTICE files exist
[ ] No unexpected binary files
[ ] All source files have ASF headers
[ ] Can compile from source
[ ] Can verify the binary build

To compile from the source, please refer to:

https://github.com/apache/pekko-connectors/tree/main?tab=readme-ov-file#building-from-source

To verify the binary build, please refer to:

https://github.com/apache/pekko-site/wiki/Pekko-Release-Process#verifying-the-binary-build

Some notes about verifying downloads can be found at:

https://pekko.apache.org/download.html#verifying-downloads

Here is my +1 (binding).

Thanks,
PJ Fanning (Apache Pekko PMC member)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org


Re: [VOTE] Release Apache Pekko Connectors 1.1.0-RC1

Posted by Arnout Engelen <en...@apache.org>.
Jep, filed https://github.com/apache/pekko-connectors/issues/952

On Tue, Jan 14, 2025 at 1:13 PM PJ Fanning <fa...@apache.org> wrote:
>
> I don't know what affects that apiUrl. I have already built 1.1.0 jars
> and the poms seem ok.
>
> https://repository.apache.org/content/groups/staging/org/apache/pekko/pekko-connectors-amqp_2.12/1.1.0/pekko-connectors-amqp_2.12-1.1.0.pom
>
> Can we just log an issue to investigate why the apiUrl is different in
> different builds? In the end, 'current' points to a 1.1 release
> anyway.
>
> On Tue, 14 Jan 2025 at 12:46, Arnout Engelen <en...@apache.org> wrote:
> >
> > On Sat, Jan 11, 2025 at 1:28 PM PJ Fanning <fa...@apache.org> wrote:
> > > https://dist.apache.org/repos/dist/dev/pekko/CONNECTORS-1.1.0-RC1/
> > > https://github.com/apache/pekko-connectors/tree/v1.1.0-RC1
> > > Git commit ID: 63f1cefac096f21a93b8ae64a395d4c6bce43caa
> > > [X] Download links are valid.
> > > [x] Checksums and signatures.
> > > [x] LICENSE/NOTICE files exist
> > > [x] No unexpected binary files
> > > [x] All source files have ASF headers
> > > [x] Can compile from source
> > > [x] Can verify the binary build
> > >
> > > https://github.com/apache/pekko-site/wiki/Pekko-Release-Process#verifying-the-binary-build
> >
> > All staged pom's info.apiURL fields (e.g. in
> > https://repository.apache.org/content/groups/staging/org/apache/pekko/pekko-connectors-amqp_2.12/1.1.0-RC1/pekko-connectors-amqp_2.12-1.1.0-RC1.pom)
> > point to https://pekko.apache.org/api/pekko-connectors/current/ while
> > if I build locally it is
> > https://pekko.apache.org/api/pekko-connectors/1.1.0-RC1/ . That would
> > be good to fix but does not need to hold up the release. PJ: do you
> > know what could've caused this or should we create an issue?
> >
> > All main jars for Scala 2.12 and 2.13 are binary reproducible.
> >
> > For Scala 3.3, I had to 'SBT_OPTS="-Xmx5g" sbt
> > +reproducibleBuildsCheck' because 'sbt ++3.3 reproducibleBuildsCheck'
> > failed to build. Here, pekko-connectors-google-fcm_3-1.1.0-RC1.jar,
> > pekko-connectors-huawei-push-kit_3-1.1.0-RC1.jar and
> > pekko-connectors-mqtt-streaming_3-1.1.0-RC1.jar didn't reproduce due
> > to https://github.com/scala/scala3/issues/21154 which indeed should be
> > fixed on 3.3.5 while we're on 3.3.4. All other jars reproduced
> > successfully.
> >
> > I have not tested the release in any project.
> >
> > This is my +1
> >
> >
> > Kind regards,
> >
> > --
> > Arnout Engelen
> > ASF Security Response
> > Apache Pekko PMC member, ASF Member
> > NixOS Committer
> > Independent Open Source consultant
> >
> > ---------------------------------------------------------------------
> > 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
>


-- 
Arnout Engelen
ASF Security Response
Apache Pekko PMC member, ASF Member
NixOS Committer
Independent Open Source consultant

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org


Re: [VOTE] Release Apache Pekko Connectors 1.1.0-RC1

Posted by PJ Fanning <fa...@apache.org>.
I don't know what affects that apiUrl. I have already built 1.1.0 jars
and the poms seem ok.

https://repository.apache.org/content/groups/staging/org/apache/pekko/pekko-connectors-amqp_2.12/1.1.0/pekko-connectors-amqp_2.12-1.1.0.pom

Can we just log an issue to investigate why the apiUrl is different in
different builds? In the end, 'current' points to a 1.1 release
anyway.

On Tue, 14 Jan 2025 at 12:46, Arnout Engelen <en...@apache.org> wrote:
>
> On Sat, Jan 11, 2025 at 1:28 PM PJ Fanning <fa...@apache.org> wrote:
> > https://dist.apache.org/repos/dist/dev/pekko/CONNECTORS-1.1.0-RC1/
> > https://github.com/apache/pekko-connectors/tree/v1.1.0-RC1
> > Git commit ID: 63f1cefac096f21a93b8ae64a395d4c6bce43caa
> > [X] Download links are valid.
> > [x] Checksums and signatures.
> > [x] LICENSE/NOTICE files exist
> > [x] No unexpected binary files
> > [x] All source files have ASF headers
> > [x] Can compile from source
> > [x] Can verify the binary build
> >
> > https://github.com/apache/pekko-site/wiki/Pekko-Release-Process#verifying-the-binary-build
>
> All staged pom's info.apiURL fields (e.g. in
> https://repository.apache.org/content/groups/staging/org/apache/pekko/pekko-connectors-amqp_2.12/1.1.0-RC1/pekko-connectors-amqp_2.12-1.1.0-RC1.pom)
> point to https://pekko.apache.org/api/pekko-connectors/current/ while
> if I build locally it is
> https://pekko.apache.org/api/pekko-connectors/1.1.0-RC1/ . That would
> be good to fix but does not need to hold up the release. PJ: do you
> know what could've caused this or should we create an issue?
>
> All main jars for Scala 2.12 and 2.13 are binary reproducible.
>
> For Scala 3.3, I had to 'SBT_OPTS="-Xmx5g" sbt
> +reproducibleBuildsCheck' because 'sbt ++3.3 reproducibleBuildsCheck'
> failed to build. Here, pekko-connectors-google-fcm_3-1.1.0-RC1.jar,
> pekko-connectors-huawei-push-kit_3-1.1.0-RC1.jar and
> pekko-connectors-mqtt-streaming_3-1.1.0-RC1.jar didn't reproduce due
> to https://github.com/scala/scala3/issues/21154 which indeed should be
> fixed on 3.3.5 while we're on 3.3.4. All other jars reproduced
> successfully.
>
> I have not tested the release in any project.
>
> This is my +1
>
>
> Kind regards,
>
> --
> Arnout Engelen
> ASF Security Response
> Apache Pekko PMC member, ASF Member
> NixOS Committer
> Independent Open Source consultant
>
> ---------------------------------------------------------------------
> 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: [VOTE] Release Apache Pekko Connectors 1.1.0-RC1

Posted by Arnout Engelen <en...@apache.org>.
On Sat, Jan 11, 2025 at 1:28 PM PJ Fanning <fa...@apache.org> wrote:
> https://dist.apache.org/repos/dist/dev/pekko/CONNECTORS-1.1.0-RC1/
> https://github.com/apache/pekko-connectors/tree/v1.1.0-RC1
> Git commit ID: 63f1cefac096f21a93b8ae64a395d4c6bce43caa
> [X] Download links are valid.
> [x] Checksums and signatures.
> [x] LICENSE/NOTICE files exist
> [x] No unexpected binary files
> [x] All source files have ASF headers
> [x] Can compile from source
> [x] Can verify the binary build
>
> https://github.com/apache/pekko-site/wiki/Pekko-Release-Process#verifying-the-binary-build

All staged pom's info.apiURL fields (e.g. in
https://repository.apache.org/content/groups/staging/org/apache/pekko/pekko-connectors-amqp_2.12/1.1.0-RC1/pekko-connectors-amqp_2.12-1.1.0-RC1.pom)
point to https://pekko.apache.org/api/pekko-connectors/current/ while
if I build locally it is
https://pekko.apache.org/api/pekko-connectors/1.1.0-RC1/ . That would
be good to fix but does not need to hold up the release. PJ: do you
know what could've caused this or should we create an issue?

All main jars for Scala 2.12 and 2.13 are binary reproducible.

For Scala 3.3, I had to 'SBT_OPTS="-Xmx5g" sbt
+reproducibleBuildsCheck' because 'sbt ++3.3 reproducibleBuildsCheck'
failed to build. Here, pekko-connectors-google-fcm_3-1.1.0-RC1.jar,
pekko-connectors-huawei-push-kit_3-1.1.0-RC1.jar and
pekko-connectors-mqtt-streaming_3-1.1.0-RC1.jar didn't reproduce due
to https://github.com/scala/scala3/issues/21154 which indeed should be
fixed on 3.3.5 while we're on 3.3.4. All other jars reproduced
successfully.

I have not tested the release in any project.

This is my +1


Kind regards,

-- 
Arnout Engelen
ASF Security Response
Apache Pekko PMC member, ASF Member
NixOS Committer
Independent Open Source consultant

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org


Re: [VOTE] Release Apache Pekko Connectors 1.1.0-RC1

Posted by kerr <he...@gmail.com>.
+1 from me

[ x] Download links are valid.
[ x] Checksums and signatures.
[ x] LICENSE/NOTICE files exist
[ x] No unexpected binary files
[ x] All source files have ASF headers
[x ] Can compile from source
[ x] Can verify the binary build test with a sample.

[success] Total time: 25 s, completed 2025年1月12日 05:01:17
何品


PJ Fanning <fa...@apache.org> 于2025年1月11日周六 20:29写道:

> Hello Pekko Community,
>
> This is a call for a vote to release Apache Pekko Connectors 1.1.0-RC1.
>
> The discussion thread:
>
> https://lists.apache.org/thread/lnjdb2xf38jxsnox1k51zw7ny3f97ot9
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/pekko/CONNECTORS-1.1.0-RC1/
>
> This release has been signed with a PGP key available here:
>
> https://downloads.apache.org/pekko/KEYS
>
> Release Notes:
>
> https://github.com/apache/pekko-connectors/pull/861/files
>
> Git tag for the release:
>
> https://github.com/apache/pekko-connectors/tree/v1.1.0-RC1
> Git commit ID: 63f1cefac096f21a93b8ae64a395d4c6bce43caa
>
> Please download, verify, and test.
>
> I have also staged jars in the Apache Nexus Repository. These were built
> with the same code as appears in this Source Release Candidate.
> I would appreciate if users could test with these too.
> If anyone finds any serious problems with these jars, please also notify us
> on this thread.
>
> https://repository.apache.org/content/groups/staging/org/apache/pekko/
>
> For sbt 1.9.4 or greater you can add this resolver
>
> resolvers += Resolver.ApacheMavenStagingRepo
>
> Otherwise for older versions of sbt
>
> resolvers += "Apache Pekko Staging" at "
> https://repository.apache.org/content/groups/staging"
>
>
> The VOTE will pass if we have more positive votes than negative votes
> and there must be a minimum of 3 approvals from Pekko PMC members.
> Anyone voting in favour of the release, could you please provide a list of
> the checks you have done?
> The vote will be left open for at least 72hrs.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about Apache Pekko, please see https://pekko.apache.org/
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] All source files have ASF headers
> [ ] Can compile from source
> [ ] Can verify the binary build
>
> To compile from the source, please refer to:
>
>
> https://github.com/apache/pekko-connectors/tree/main?tab=readme-ov-file#building-from-source
>
> To verify the binary build, please refer to:
>
>
> https://github.com/apache/pekko-site/wiki/Pekko-Release-Process#verifying-the-binary-build
>
> Some notes about verifying downloads can be found at:
>
> https://pekko.apache.org/download.html#verifying-downloads
>
> Here is my +1 (binding).
>
> Thanks,
> PJ Fanning (Apache Pekko PMC member)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>

Re: [VOTE] Release Apache Pekko Connectors 1.1.0-RC1

Posted by Nicolas Vollmar <nv...@gmail.com>.
+1 from me

[x] Download links are valid.
[x] Checksums and signatures.
[x] LICENSE/NOTICE files exist
[x] No unexpected binary files
[x] All source files have ASF headers
[x] Can compile from source
[x] Can verify the binary build

> On 11 Jan 2025, at 13:28, PJ Fanning <fa...@apache.org> wrote:
> 
> Hello Pekko Community,
> 
> This is a call for a vote to release Apache Pekko Connectors 1.1.0-RC1.
> 
> The discussion thread:
> 
> https://lists.apache.org/thread/lnjdb2xf38jxsnox1k51zw7ny3f97ot9
> 
> The release candidate:
> 
> https://dist.apache.org/repos/dist/dev/pekko/CONNECTORS-1.1.0-RC1/
> 
> This release has been signed with a PGP key available here:
> 
> https://downloads.apache.org/pekko/KEYS
> 
> Release Notes:
> 
> https://github.com/apache/pekko-connectors/pull/861/files
> 
> Git tag for the release:
> 
> https://github.com/apache/pekko-connectors/tree/v1.1.0-RC1
> Git commit ID: 63f1cefac096f21a93b8ae64a395d4c6bce43caa
> 
> Please download, verify, and test.
> 
> I have also staged jars in the Apache Nexus Repository. These were built
> with the same code as appears in this Source Release Candidate.
> I would appreciate if users could test with these too.
> If anyone finds any serious problems with these jars, please also notify us
> on this thread.
> 
> https://repository.apache.org/content/groups/staging/org/apache/pekko/
> 
> For sbt 1.9.4 or greater you can add this resolver
> 
> resolvers += Resolver.ApacheMavenStagingRepo
> 
> Otherwise for older versions of sbt
> 
> resolvers += "Apache Pekko Staging" at "
> https://repository.apache.org/content/groups/staging"
> 
> 
> The VOTE will pass if we have more positive votes than negative votes
> and there must be a minimum of 3 approvals from Pekko PMC members.
> Anyone voting in favour of the release, could you please provide a list of
> the checks you have done?
> The vote will be left open for at least 72hrs.
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> To learn more about Apache Pekko, please see https://pekko.apache.org/
> 
> Checklist for reference:
> 
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] All source files have ASF headers
> [ ] Can compile from source
> [ ] Can verify the binary build
> 
> To compile from the source, please refer to:
> 
> https://github.com/apache/pekko-connectors/tree/main?tab=readme-ov-file#building-from-source
> 
> To verify the binary build, please refer to:
> 
> https://github.com/apache/pekko-site/wiki/Pekko-Release-Process#verifying-the-binary-build
> 
> Some notes about verifying downloads can be found at:
> 
> https://pekko.apache.org/download.html#verifying-downloads
> 
> Here is my +1 (binding).
> 
> Thanks,
> PJ Fanning (Apache Pekko PMC member)
> 
> ---------------------------------------------------------------------
> 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