You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@plc4x.apache.org by Christofer Dutz <ch...@c-ware.de> on 2025/08/06 19:49:50 UTC
[VOTE] Apache PLC4X Extras 0.13.0 RC1
Apache PLC4X Extras 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.13.0
Hash for the release tag: 6e351645552de7c11482fc31dda5dd4aa92ef02f
Per [3] "Before voting +1 PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases."
You can achieve the above by following [4].
[ ] +1 accept (indicate what you validated - e.g. performed the non-RM items in [4])
[ ] -1 reject (explanation required)
[1] https://repository.apache.org/content/repositories/orgapacheplc4x-1060
[2] https://dist.apache.org/repos/dist/dev/plc4x/plc4x-extras/0.13.0/rc1/
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
AW: [VOTE] Apache PLC4X Extras 0.13.0 RC1
Posted by Christofer Dutz <ch...@c-ware.de>.
-1 (PMC/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 LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
[MINOR] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
- Typo in the maven command … should be ./mvnw and not .mvnw
[OK] [RM] Run RAT externally to ensure there are no surprises.
[OK] Search for SNAPSHOT references
[OK] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file.
[FAIL] Build the project according to the information in the README.md file.
*
I was unable to build the wifi-1 plugin as the build version plugin fails because of missing git metadata.
Von: Christofer Dutz <ch...@c-ware.de>
Datum: Mittwoch, 6. August 2025 um 21:50
An: dev@plc4x.apache.org <de...@plc4x.apache.org>
Betreff: [VOTE] Apache PLC4X Extras 0.13.0 RC1
Apache PLC4X Extras 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.13.0
Hash for the release tag: 6e351645552de7c11482fc31dda5dd4aa92ef02f
Per [3] "Before voting +1 PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases."
You can achieve the above by following [4].
[ ] +1 accept (indicate what you validated - e.g. performed the non-RM items in [4])
[ ] -1 reject (explanation required)
[1] https://repository.apache.org/content/repositories/orgapacheplc4x-1060
[2] https://dist.apache.org/repos/dist/dev/plc4x/plc4x-extras/0.13.0/rc1/
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release