I agree we must make it mandatory for the committer (us) to squash it.
But not really mandatory to ask contributor to squash but just only use the
"Squash and merge" option and you will get proper commit on merge:
see this commit
https://github.com/apache/maven-javadoc-plugin/commit/f92b508c26945a0
+1
reproducibility verified: little issue found on source-release.zip, with
strange generated file added, but nothing serious
mvn -Papache-release clean verify buildinfo:save -Dgpg.skip
-Dreference.repo=https://repository.apache.org/content/repositories/maven-1557
Regards,
Hervé
- Mail o
Hi,
On 13.03.20 15:58, Michael Osipov wrote:
Am 2020-03-12 um 19:46 schrieb Robert Scholte:
This week I was very surprised to see commits from the user call
"github" in Jenkins:
https://builds.apache.org/job/maven-box/job/maven-shared-utils/job/master/changes
IMO we shouldn't want these kind
Am 2020-03-12 um 19:46 schrieb Robert Scholte:
This week I was very surprised to see commits from the user call "github" in
Jenkins:
https://builds.apache.org/job/maven-box/job/maven-shared-utils/job/master/changes
IMO we shouldn't want these kind of commits.
Based on the most recent activitie
Infra changed the hostname and url to subscribe to so the plugin is being
updated... until then you’re relying on polling every 8h or something like
that
On Thu 12 Mar 2020 at 20:37, Elliotte Rusty Harold
wrote:
> Thanks. It did eventually kick off, but it certainly wasn't immediate,
> more like