Skip to:
The key used to sign testNG changed for release 7.5
The testNG update got committed accidentally to the parent pom prior to validating the key and unpicking the change is difficult at this stage,
Before we ship 11.3.0 of the parent pom this key needs to be “validated”.
We are developing the process on the fly but what has been done so far is
Check for the key on a website or in the usual places (on a website or in the SCM)
Contact the owner by email
Discuss among the committers prior to doing something else of a leap of faith TOFU.
Marking this as a blocker
Got confirming mail from Cedric
Stage (1) Look for it at the “usual places” has not yielded anything
Mail sent to key owner (cedric@beust.com).
cedric@beust.com
Note that there is google-evidence of other accepting this key into their key checking infrastructure.
The key used to sign testNG changed for release 7.5
The testNG update got committed accidentally to the parent pom prior to validating the key and unpicking the change is difficult at this stage,
Before we ship 11.3.0 of the parent pom this key needs to be “validated”.
We are developing the process on the fly but what has been done so far is
Check for the key on a website or in the usual places (on a website or in the SCM)
Contact the owner by email
Discuss among the committers prior to doing something else of a leap of faith TOFU.
Marking this as a blocker