BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [1890]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/1890/;>PLC4X/PLC4X/develop
[develop] [1890]"
Apache PLC4X 0.13.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: v0.12.0
Hash for the
+1 (binding)
Chris
[OK] Download all staged artifacts under the url specified in the release vote
email.
[OK] Verify the signature is correct.
[OK] Check if the signature references an Apache email address.
[OK] Verify the SHA512 hashes.
[OK] Unzip the archive.
[OK] Verify the existence of
This is the discussion thread for the corresponding VOTE thread.
Please keep discussions in this thread to simplify the counting of votes.
If you have to vote -1 please mention a brief description on why and then take
the details to this thread.
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [1889]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/1889/;>PLC4X/PLC4X/develop
[develop] [1889]"
+1 (binding)
Lukas - otluk
[x] Download all staged artifacts under the url specified in the release
vote email.
[x] Verify the signature is correct.
[x] Check if the signature references an Apache email address.
[x] Verify the SHA512 hashes.
[x] Unzip the archive.
[x] Verify the existence of
Chris,
I created a fresh instance of the plc4x project and ran
./mvnw -P update-generated-code,.os-mac-x86_64,skip-prerequisite-check -pl
:plc4j-driver-eip -am clean package
which ran to completion and regenerated the files. As a sanity check I
updated the eip.mspec with one of my changes
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [1883]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/1883/;>PLC4X/PLC4X/develop
[develop] [1883]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [1886]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/1886/;>PLC4X/PLC4X/develop
[develop] [1886]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [1888]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/1888/;>PLC4X/PLC4X/develop
[develop] [1888]"
-1 (binding)
Chris
[OK] Download all staged artifacts under the url specified in the release vote
email.
[OK] Verify the signature is correct.
[OK] Check if the signature references an Apache email address.
[OK] Verify the SHA512 hashes.
[OK] Unzip the archive.
[OK] Verify the existence of
Found an issue … will fix it and stage an RC2
Chris
Von: Christofer Dutz
Datum: Freitag, 16. Februar 2024 um 14:54
An: dev@plc4x.apache.org
Betreff: AW: [VOTE] Apache PLC4X 0.12.0 RC1
-1 (binding)
Chris
[OK] Download all staged artifacts under the url specified in the release vote
email.
Apache PLC4X 0.12.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: v0.12.0
Hash for the
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [1887]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/1887/;>PLC4X/PLC4X/develop
[develop] [1887]"
This is the discussion thread for the corresponding VOTE thread.
Please keep discussions in this thread to simplify the counting of votes.
If you have to vote -1 please mention a brief description on why and then take
the details to this thread.
BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [1884]':
Is back to normal.
-1 (binding)
Found the mentioned issue and can confirm that I can not build from source.
Lukas
[OK] Download all staged artifacts under the url specified in the release
vote email.
[OK] Verify the signature is correct.
[OK] Check if the signature references an Apache email address.
[OK] Verify
Hi all,
this release was the first done by the scripts in “tools”. With this I am
trying to make releasing easier and to make it harder for RMs to miss things.
However, the probably major difference is that the final
release:perform-release step is executed in a Docker-container, which should
18 matches
Mail list logo