The vote has now closed. The results are:

Positive Binding Votes: 3

Niklas Merz
Norman Breau
Tim Brust

Negative Binding Votes: 0

Other Votes: 0

The vote has passed.

On April 5, 2022, Tim Brust <tim.br...@sinnerschrader.com> wrote:
> I vote +1, thanks for the release, Niklas!
>
>
>  * Changes look good
>  * Coho verify archive
>  * Coho verify tags
>
> --
> Tim Brust, Senior Product Engineer
>
> tim.br...@sinnerschrader.com<mailto:tim.br...@sinnerschrader.com>
>
> SinnerSchrader Deutschland GmbH
> Part of Accenture Interactive
> Völckersstraße 38, 22765 Hamburg, Germany
>
> Amtsgericht Hamburg HRB-Nr. 63663
>
> Geschäftsführung: Dr. Axel Averdung (Sprecher),
> Holger Blank, Philipp Kafkoulas, Florian Langmack, Sven Schmiede
>
> Büros: Berlin, Hamburg, Frankfurt a. M., München, Prag
>
> www.sinnerschrader.com<https://www.sinnerschrader.com/> | NEXT AGENCY
>
> From: Norman Breau <nor...@normanbreau.com>
> Date: Tuesday, 5. April 2022 at 02:14
> To: dev@cordova.apache.org <dev@cordova.apache.org>
> Subject: [External] Re: [VOTE] cordova-plugin-splashscreen release
> 6.0.1 patch release
> This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly
> with links and attachments.
>
> I vote +1:
>
> - Verified Tags
> - Verified archive
> - Tests appears green
>
> On 2022-04-04 3:46 p.m., Niklas Merz wrote:
> > Please review and vote on the release of the splashscreen plugin
> > by replying to this email (and keep discussion on the DISCUSS
> thread)
> >
> > The plugins have been published to dist/dev:
> > https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__dist.apache.org_repos_dist_dev_cordova_splashscreen-
> 2D6.0.1_&d=DwICaQ&c=eIGjsITfXP_y-
> DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=cpdalg2AkAkNwsuGb83Rn1F0oaw9obXe_cnaIOV4Wow&m=sx_SQVZ95iWQrwQKHOuJD2MxQZogzc7XcZW0ivz5gFtAU96AaEphKG7He2D_NMV6&s=TmRBzr2hABGi6BFbr706wlF0sIMAYlRg6t4JLO4DUwY&e=
> >
> > The packages were published from their corresponding git tags:
> > cordova-plugin-splashscreen: 6.0.1 (35c22a8a1a)
> >
> > Upon a successful vote I will upload the archives to dist/, upload
> them
> > to npm, and post the corresponding blog post.
> >
> > Voting guidelines: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_apache_cordova-2D&d=DwICaQ&c=eIGjsITfXP_y-
> DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=cpdalg2AkAkNwsuGb83Rn1F0oaw9obXe_cnaIOV4Wow&m=sx_SQVZ95iWQrwQKHOuJD2MxQZogzc7XcZW0ivz5gFtAU96AaEphKG7He2D_NMV6&s=l4N8B6wd2Ip5q_e6OY2FSupymBw-
> QVu5aoyrsakTnT0&e=
> > coho/blob/master/docs/release-voting.md
> > How to vote on a plugins release at
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_apache_cordova-2D&d=DwICaQ&c=eIGjsITfXP_y-
> DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=cpdalg2AkAkNwsuGb83Rn1F0oaw9obXe_cnaIOV4Wow&m=sx_SQVZ95iWQrwQKHOuJD2MxQZogzc7XcZW0ivz5gFtAU96AaEphKG7He2D_NMV6&s=l4N8B6wd2Ip5q_e6OY2FSupymBw-
> QVu5aoyrsakTnT0&e=
> > coho/blob/master/docs/plugins-release-process.md#voting
> > Vote checklist for easy reference:
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_apache_cordova-2D&d=DwICaQ&c=eIGjsITfXP_y-
> DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=cpdalg2AkAkNwsuGb83Rn1F0oaw9obXe_cnaIOV4Wow&m=sx_SQVZ95iWQrwQKHOuJD2MxQZogzc7XcZW0ivz5gFtAU96AaEphKG7He2D_NMV6&s=l4N8B6wd2Ip5q_e6OY2FSupymBw-
> QVu5aoyrsakTnT0&e=
> > coho/blob/master/docs/vote-checklist.md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and
> subdependencies
> > have Apache-compatible licenses
> > * Ensured continuous build was green when repos were tagged - CI
> only
> > fails for emulator not coming up
> > * No NPM audit issues
> > * Short test with testapp
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
> ________________________________
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete
> the original. Any other use of the email by you is prohibited.

Reply via email to