Went through the checklist, so far everything looks good

+1 from me


On Tue, 19 Dec 2023 at 01:15, Matthew de Detrich
<[email protected]> wrote:

> I have gone through the checklist, i.e.
>
> [x] Download links are valid.
> [x] Checksums and signatures.
> [x] LICENSE/NOTICE files exist
> [x] No unexpected binary files
> [x] Source files have ASF headers
> [x] Can compile from source
>
> Also gpg verified the detached signatures from the binary release as well
> as the binaries themselves with jardiff
>
> +1 from me
>
> On Tue, Dec 19, 2023 at 8:18 AM PJ Fanning <[email protected]> wrote:
>
> > Would any Pekko PPMC members be in a position to review this RC?
> >
> >
> > On 2023/12/09 20:25:16 PJ Fanning wrote:
> > > Hello Pekko Community,
> > >
> > > This is a call for a vote to release Apache Pekko(incubating)
> > > Persistence R2DBC version 1.0.0-RC1.
> > >
> > > The discussion thread:
> > >
> > > https://lists.apache.org/thread/108tfnxofmp5bvq9y60pmwn34d6bs5s6
> > >
> > > The release candidate:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/pekko/PERSISTENCE-R2DBC-1.0.0-RC1/
> > >
> > > This release has been signed with a PGP key, available here:
> > >
> > > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> > >
> > > Git branch for the release:
> > >
> > >
> >
> https://github.com/apache/incubator-pekko-persistence-r2dbc/tree/v1.0.0-RC1
> > > Git commit ID: 3fc28f10a4570c9834495fef1d104a2dbd07fb44
> > >
> > > Please download, verify, and test.
> > >
> > > We have also staged jars in the Apache Nexus Repository. These were
> > > built with the same code
> > > as appears in this Source Release Candidate. We 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/
> > >
> > > In sbt, you can add this resolver.
> > >
> > > 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 PPMC 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 until at least 20:00 UTC on 12 December
> 2023.
> > >
> > > [ ] +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
> > > [ ] Source files have ASF headers
> > > [ ] Can compile from source
> > >
> > > To compile from the source, please refer to:
> > >
> > >
> >
> https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source
> > >
> > > Some of the tests rely on postgresql running locally on port 5432 and
> > > the DDL is at ddl-scripts/create_tables_postgres.sql
> > >
> > > Some notes about verifying downloads can be found at:
> > >
> > > https://pekko.apache.org/download.html#verifying-downloads
> > >
> > >
> > > Here is my +1.
> > >
> > > Thanks,
> > >
> > > PJ Fanning (Apache Pekko PPMC member)
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>
> --
>
> 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:* [email protected]
>

Reply via email to