Thanks Tim. I think most users read the the releasnotes on GitHub and
the blog. I fixed it there. Therefore I also think this not a reason to
do the release again.

On April 5, 2022, Tim Brust <tim.br...@sinnerschrader.com> wrote:
> One minor nit that can be changed in a follow up commit:
> In the RELEASENOTES.md file a space is missing after the [GH-xxx] link
> and the short text.
>
> --
> 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: Niklas Merz <niklasm...@apache.org>
> Date: Saturday, 2. April 2022 at 13:15
> To: dev@cordova.apache.org <dev@cordova.apache.org>
> Subject: [External] [DISCUSS] cordova-plugin-splashscreen release
> 6.0.1
> This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly
> with links and attachments.
>
> Does anyone have any reason to delay a small patch release?
>
> Any outstanding patches to land? I created a milestone with patches to
> review: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_apache_cordova-2Dplugin-2D&d=DwICaQ&c=eIGjsITfXP_y-
> DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=cpdalg2AkAkNwsuGb83Rn1F0oaw9obXe_cnaIOV4Wow&m=ktkWIkHoXqUsMLYc1__bNSR0337YLSJaxz8M8E6tX_EuuH-
> hBMMtFqDoutef8kZl&s=OqSPZNbqCSr4TUkflE5hBwhp2rn684gaEFOtgxTGQaY&e=
> splashscreen/milestone/4
>
> If not, I will start the release in the next days.
>
> ________________________________
>
> 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