plc4x-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <>
Subject Re: [VOTE] Apache PLC4X (Incubating) 0.3.0 RC1
Date Thu, 24 Jan 2019 14:40:27 GMT
-1 (binding) chris

The RELEASE_NOTES don't reference the proper release version and it contains the prefix "(Unreleased)".

Besides this, I did the full check:
- tools/ 0.3.0 1 (Downloaded and verified, after I removed the download
of MD5 which we removed in the last release)
- Signatures check out
- Signature is from an apache email
- Julians key is correctly added to the KEYS file
- DISCLAIMER, LICENSE, NOTICE, README seem correct (from my point of view)
- Year was adjusted to 2019
- rat.txt doesn't contain anything unexpected
- did a check for the existence of "SNAPSHOT" in pom.xml files and I found some where I would
like to have them matching the rest (Would have to be done manually, but that's up to the
	- plc4cpp
	- plc4cpp/api
	- plc4cpp/libs
	- examples/hello-connectivity-mqtt (here only the project, not the mqtt-bee dependency) 

The reason for me liking to have at least the cpp modules in the same version is that if someone
would build with the "with-cpp" option, it would include these modules and they would reference
the parent pom in its SNAPSHOT version.

As soon as the RELEASE_NOTES issue is addressed, I'll change my vote to a "+1"


Am 24.01.19, 14:31 schrieb "Julian Feinauer" <>:

    Apache PLC4X (Incubating) 0.3.0 has been staged under [2] and it’s time to vote
    on accepting it for release.  All Maven artifacts are available under [1].
    If approved we will seek final release approval from the IPMC.
    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.3.0
    Hash for the release tag: 904eba469ac20b61b37ca4b394baac936434945d
    Per [3] "Before voting +1 [P]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)

View raw message