+1   but I have one negative remark to the tradition with "Merge pull
request". If you watch the code, you would think that the project
duplicates some code, but it is not real. Whole problem is with these Merge
requests because they join several commits together, you type some comments
to the developers about code duplicates but then you realise that the Merge
Requests are totally messy and you are not able to separate PR changes from
the changes of other PRs or colleagues. Here is the history:

https://github.com/apache/maven-gpg-plugin/commits/master


T

On Wed, May 5, 2021 at 6:46 PM Hervé BOUTEMY <[email protected]> wrote:

> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317521&version=12348086&styleName=Text
>
> in addition to the cancelled 3.0.0 release candidate that solved 13 other
> issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317521&version=12330781&styleName=Text
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1645/
>
> https://repository.apache.org/content/repositories/maven-1645/org/apache/maven/plugins/maven-gpg-plugin/3.0.1/maven-gpg-plugin-3.0.1-source-release.zip
>
> Source release checksum(s):
> maven-gpg-plugin-3.0.1-source-release.zip sha512:
> 10eef9c1f3e71724b328e0f8d76303d251922a4e7a05ffbbe44191e2293c097e976b0f6b7ec3b8783b04da13c74bbe5b34f4dabc5e0dd3a7cb5fe7aa92122af0
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-gpg-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to