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 2021/09/08 18:17:14 UTC
[VOTE] Apache PLC4X Build-Tools Code-Generation 1.5.0 RC1
Apache PLC4X Build-Tools Code-Generation 1.5.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.
Repository: https://gitbox.apache.org/repos/asf/plc4x-build-tools.git
Release tag: releases/code-generation/1.5.0
Hash for the release tag: e0f1569f74ad00af15e4a984efa0cc8ffbae85d1
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-1034
[2] https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.5.0/rc1/
[3] https://www.apache.org/dev/release/validation.html#approving-a-release
[4] https://plc4x.apache.org/developers/release/validation.html
AW: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.5.0 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.
[OK] [RM] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle.
[OK] [RM] Run RAT externally to ensure there are no surprises.
[OK] Search for SNAPSHOT references: Only found some in the dummy website copy in the integration-tests
[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.
[OK] [RM] Build the project with all with-xyz profiles and tests enabled and an empty maven local repo.
-----Ursprüngliche Nachricht-----
Von: Lukas Ott <ot...@gmail.com>
Gesendet: Donnerstag, 9. September 2021 09:05
An: dev@plc4x.apache.org
Betreff: Re: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.5.0 RC1
+1 (binding)
Actions performed:
Downloaded all staged artifacts under the url specified in the release vote email into a directory we’ll now call download-dir.
Verified the signature is correct
gpg: Korrekte Signatur von "Christofer Dutz (Apache Comitter) < cdutz@apache.org>"
Verified the SHA512 hashes
Verified the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
Verified the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
Run RAT externally with no surprises
Successfully built with Ubuntu 20.04 and openjdk 11.0.11 2021-04-20 OpenJDK Runtime Environment (build 11.0.11+9-Ubuntu-0ubuntu2.20.04)
Am Mi., 8. Sept. 2021 um 20:17 Uhr schrieb Christofer Dutz <
christofer.dutz@c-ware.de>:
> Apache PLC4X Build-Tools Code-Generation 1.5.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.
>
> Repository: https://gitbox.apache.org/repos/asf/plc4x-build-tools.git
> Release tag: releases/code-generation/1.5.0
> Hash for the release tag: e0f1569f74ad00af15e4a984efa0cc8ffbae85d1
>
> 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-1034
> [2]
> https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.5.0/rc1/
> [3]
> https://www.apache.org/dev/release/validation.html#approving-a-release
> [4] https://plc4x.apache.org/developers/release/validation.html
>
Re: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.5.0 RC1
Posted by Lukas Ott <ot...@gmail.com>.
+1 (binding)
Actions performed:
Downloaded all staged artifacts under the url specified in the release vote
email into a directory we’ll now call download-dir.
Verified the signature is correct
gpg: Korrekte Signatur von "Christofer Dutz (Apache Comitter) <
cdutz@apache.org>"
Verified the SHA512 hashes
Verified the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in
the extracted source bundle.
Verified the content of LICENSE, NOTICE, README, RELEASE_NOTES files in
the extracted source bundle.
Run RAT externally with no surprises
Successfully built with Ubuntu 20.04 and
openjdk 11.0.11 2021-04-20
OpenJDK Runtime Environment (build 11.0.11+9-Ubuntu-0ubuntu2.20.04)
Am Mi., 8. Sept. 2021 um 20:17 Uhr schrieb Christofer Dutz <
christofer.dutz@c-ware.de>:
> Apache PLC4X Build-Tools Code-Generation 1.5.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.
>
> Repository: https://gitbox.apache.org/repos/asf/plc4x-build-tools.git
> Release tag: releases/code-generation/1.5.0
> Hash for the release tag: e0f1569f74ad00af15e4a984efa0cc8ffbae85d1
>
> 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-1034
> [2]
> https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.5.0/rc1/
> [3]
> https://www.apache.org/dev/release/validation.html#approving-a-release
> [4] https://plc4x.apache.org/developers/release/validation.html
>
Re: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.5.0 RC1
Posted by Niklas Merz <ni...@apache.org>.
+1 (non-binding)
I checked:
- Release tag
- Hash and signature
- Tests and build successful locally
- Rat looks ok
On 2021/09/08 18:17:14, Christofer Dutz <ch...@c-ware.de>
wrote:
> Apache PLC4X Build-Tools Code-Generation 1.5.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.
>
> Repository: https://gitbox.apache.org/repos/asf/plc4x-build-tools.git
> Release tag: releases/code-generation/1.5.0
> Hash for the release tag: e0f1569f74ad00af15e4a984efa0cc8ffbae85d1
>
> 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-
1034
> [2] https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-
generation/1.5.0/rc1/
> [3] https://www.apache.org/dev/release/validation.html#approving-a-
release
> [4] https://plc4x.apache.org/developers/release/validation.html
>
Re: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.5.0 RC1
Posted by Julian Feinauer <jf...@apache.org>.
+1 (binding)
I checked:
- Signatures and Hashes
- Content of README and RELEASE_NOTES (same strange behavior with README as stated in slack, line encodings seem to be different in zip and in svn)
- Files in svn are similar to those in artefact
- Builds on my system via mvn clean install
Thanks for the work Chris!
Julian
On 2021/09/08 18:17:14, Christofer Dutz <ch...@c-ware.de> wrote:
> Apache PLC4X Build-Tools Code-Generation 1.5.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.
>
> Repository: https://gitbox.apache.org/repos/asf/plc4x-build-tools.git
> Release tag: releases/code-generation/1.5.0
> Hash for the release tag: e0f1569f74ad00af15e4a984efa0cc8ffbae85d1
>
> 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-1034
> [2] https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.5.0/rc1/
> [3] https://www.apache.org/dev/release/validation.html#approving-a-release
> [4] https://plc4x.apache.org/developers/release/validation.html
>