You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@plc4x.apache.org by Sebastian Rühl <sr...@apache.org> on 2025/09/01 07:38:22 UTC
Re: [VOTE] Apache PLC4X Extras 0.13.1 RC1
+1 (binding)
sruehl
[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 LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
[x] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
[x] Search for SNAPSHOT references
[x] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file.
[x] Build the project according to the information in the README.md file.
On 2025/08/29 15:07:01 Christofer Dutz wrote:
> Apache PLC4X Extras 0.13.1 RC1 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.1
> Hash for the release tag: d87d3b4589047141d416301a43963d729447e41c
>
> 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-1063
> [2] https://dist.apache.org/repos/dist/dev/plc4x/plc4x-extras/0.13.1/rc1/
> [3] https://www.apache.org/dev/release.html#approving-a-release
> [4] https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
>
>
>
[RESULT][VOTE] Apache PLC4X Extras 0.13.1 RC1
Posted by Christofer Dutz <ch...@c-ware.de>.
(Again with the right subject)
So the vote passes with 3 binding +1 votes.
Lukas Ott
Sebastian Rühl
Christofer Dutz
Thanks for taking the time for yet another vote in such a short period of time.
Chris
Von: Christofer Dutz <ch...@c-ware.de>>
Datum: Dienstag, 2. September 2025 um 08:29
An: dev@plc4x.apache.org<ma...@plc4x.apache.org> <de...@plc4x.apache.org>>
Betreff: AW: [VOTE] Apache PLC4X Extras 0.13.1 RC1
+1 (binding)
Chris
Von: Christofer Dutz <ch...@c-ware.de>
Datum: Dienstag, 2. September 2025 um 08:30
An: dev@plc4x.apache.org <de...@plc4x.apache.org>
Betreff: AW: [VOTE] Apache PLC4X Extras 0.13.1 RC1
So the vote passes with 3 binding +1 votes.
*
Lukas Ott
*
Sebastian Rühl
*
Christofer Dutz
Thanks for taking the time for yet another vote in such a short period of time.
Chris
Von: Christofer Dutz <ch...@c-ware.de>
Datum: Dienstag, 2. September 2025 um 08:29
An: dev@plc4x.apache.org <de...@plc4x.apache.org>
Betreff: AW: [VOTE] Apache PLC4X Extras 0.13.1 RC1
+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 LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
[OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
[MINOR] [RM] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle.
*
Mvnw command missing a slash
[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.
[OK] Build the project according to the information in the README.md file.
Von: Sebastian Rühl <sr...@apache.org>
Datum: Montag, 1. September 2025 um 09:38
An: dev@plc4x.apache.org <de...@plc4x.apache.org>
Betreff: Re: [VOTE] Apache PLC4X Extras 0.13.1 RC1
+1 (binding)
sruehl
[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 LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
[x] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
[x] Search for SNAPSHOT references
[x] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file.
[x] Build the project according to the information in the README.md file.
On 2025/08/29 15:07:01 Christofer Dutz wrote:
> Apache PLC4X Extras 0.13.1 RC1 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.1
> Hash for the release tag: d87d3b4589047141d416301a43963d729447e41c
>
> 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-1063
> [2] https://dist.apache.org/repos/dist/dev/plc4x/plc4x-extras/0.13.1/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.1 RC1
Posted by Christofer Dutz <ch...@c-ware.de>.
So the vote passes with 3 binding +1 votes.
*
Lukas Ott
*
Sebastian Rühl
*
Christofer Dutz
Thanks for taking the time for yet another vote in such a short period of time.
Chris
Von: Christofer Dutz <ch...@c-ware.de>
Datum: Dienstag, 2. September 2025 um 08:29
An: dev@plc4x.apache.org <de...@plc4x.apache.org>
Betreff: AW: [VOTE] Apache PLC4X Extras 0.13.1 RC1
+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 LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
[OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
[MINOR] [RM] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle.
*
Mvnw command missing a slash
[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.
[OK] Build the project according to the information in the README.md file.
Von: Sebastian Rühl <sr...@apache.org>
Datum: Montag, 1. September 2025 um 09:38
An: dev@plc4x.apache.org <de...@plc4x.apache.org>
Betreff: Re: [VOTE] Apache PLC4X Extras 0.13.1 RC1
+1 (binding)
sruehl
[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 LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
[x] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
[x] Search for SNAPSHOT references
[x] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file.
[x] Build the project according to the information in the README.md file.
On 2025/08/29 15:07:01 Christofer Dutz wrote:
> Apache PLC4X Extras 0.13.1 RC1 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.1
> Hash for the release tag: d87d3b4589047141d416301a43963d729447e41c
>
> 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-1063
> [2] https://dist.apache.org/repos/dist/dev/plc4x/plc4x-extras/0.13.1/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.1 RC1
Posted by Christofer Dutz <ch...@c-ware.de>.
+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 LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
[OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
[MINOR] [RM] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle.
*
Mvnw command missing a slash
[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.
[OK] Build the project according to the information in the README.md file.
Von: Sebastian Rühl <sr...@apache.org>
Datum: Montag, 1. September 2025 um 09:38
An: dev@plc4x.apache.org <de...@plc4x.apache.org>
Betreff: Re: [VOTE] Apache PLC4X Extras 0.13.1 RC1
+1 (binding)
sruehl
[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 LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
[x] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
[x] Search for SNAPSHOT references
[x] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file.
[x] Build the project according to the information in the README.md file.
On 2025/08/29 15:07:01 Christofer Dutz wrote:
> Apache PLC4X Extras 0.13.1 RC1 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.1
> Hash for the release tag: d87d3b4589047141d416301a43963d729447e41c
>
> 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-1063
> [2] https://dist.apache.org/repos/dist/dev/plc4x/plc4x-extras/0.13.1/rc1/
> [3] https://www.apache.org/dev/release.html#approving-a-release
> [4] https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
>
>
>