nm, the keys are in the standard location :
https://dist.apache.org/repos/dist/release/plc4x/KEYS
On May 15, 2020 at 23:18:24, Otto Fowler (ottobackwa...@gmail.com) wrote:
Where is the KEYS file for this project?
On May 15, 2020 at 12:52:01, Christofer Dutz (christofer.d...@c-ware.de)
wrote:
Where is the KEYS file for this project?
On May 15, 2020 at 12:52:01, Christofer Dutz (christofer.d...@c-ware.de)
wrote:
Apache PLC4X 0.7.0 has been staged under [2] and it’s time to vote
on accepting it for release. All Maven artifacts are available under [1].
Voting will be open for 72hr.
A mi
+1
Tasks i did:
- Downloaded all staged artifacts
- Checked if the signature references an Apache email address (gpg --verify)
- Verified the SHA512 hashes
- Verified the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in
the extracted source bundle.
- Verified the content of LICENSE, NO
Apache PLC4X 0.7.0 has been staged under [2] and it’s time to vote
on accepting it for release. All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.
Release tag: release/0.7.0
Hash for
BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [879]':
Is back to normal.
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [878]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/878/";>PLC4X/PLC4X/develop
[develop] [878]"
BUILD-UNSTABLE: Job 'PLC4X/PLC4X/develop [develop] [877]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/877/";>PLC4X/PLC4X/develop
[develop] [877]"
ottobackwards closed pull request #156:
URL: https://github.com/apache/plc4x/pull/156
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go t
ottobackwards commented on pull request #156:
URL: https://github.com/apache/plc4x/pull/156#issuecomment-629273548
never mind
This is an automated message from the Apache Git Service.
To respond to the message, please log on
BUILD-UNSTABLE: Job 'PLC4X/PLC4X/develop [develop] [876]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/876/";>PLC4X/PLC4X/develop
[develop] [876]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [875]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/875/";>PLC4X/PLC4X/develop
[develop] [875]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [874]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/874/";>PLC4X/PLC4X/develop
[develop] [874]"
ottobackwards commented on pull request #156:
URL: https://github.com/apache/plc4x/pull/156#issuecomment-629213899
OK, I'll add that.
This is an automated message from the Apache Git Service.
To respond to the message, please
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [873]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/873/";>PLC4X/PLC4X/develop
[develop] [873]"
chrisdutz commented on pull request #156:
URL: https://github.com/apache/plc4x/pull/156#issuecomment-629095235
The thing with this is that now you can't build without tests ... I
intentionally built it that way, that you can do a maven build and skip tests
...
---
chrisdutz commented on pull request #156:
URL: https://github.com/apache/plc4x/pull/156#issuecomment-629095469
Perhaps inverting the logic and allowing to disable tests would be an option
...
This is an automated message fro
16 matches
Mail list logo