Hi Andreas, thank you very much for your support (as I know to few about TIA programming to do it myself with our PLC here). I will try to dig into some of them the end of this or next week (if chris doesn’t do it first : )).
I suggest to get the release going none the less (I think this is the usual way) and have a bugfix release soon (0.1.1) where such things are fixed. @chris: How is the procedure for hotfix releases (in semVer)? Always the same procedure? Julian Am 25.09.18, 14:12 schrieb "Uschold Andreas" <[email protected]>: I just did some tests with the S7 driver and found a couple of issues. PLC4X-56 [S7] S7Field does not recognize addresses with numElements present PLC4X-57 [S7] Response for address with numElements contains only first item PLC4X-58 [S7] Reading more then PDU with one request blocks calling thread indefinitly PLC4X-59 [S7] Reading a UDINT with value 0x00000000 and non positive floating point values does not work I found these issues while testing exotic / exceptional constellations, so for "normal" use cases they are probably not an issue. Andreas -----Ursprüngliche Nachricht----- Von: Julian Feinauer [mailto:[email protected]] Gesendet: Montag, 24. September 2018 21:04 An: [email protected] Betreff: [EXT] Re: [VOTE] Apache PLC4X (Incubating) 0.1.0 RC2 +1 (contributor) Checks and build performed on Mac OS X. Checks performed: - Checked out using the new tooling: OK - Checked signatures: OK - Checked the zip correctly unpacks to the expected directory structure: OK - verify the existence of DISCLAIMER, LICENSE, NOTICE, README, RELEASE_NOTES: OK - Built from sources (including tests) according to instructions in README: OK - All tests pass: OK Julian Am 24.09.18, 16:39 schrieb "Stefan Bodewig" <[email protected]>: On 2018-09-22, Christofer Dutz wrote: > Apache PLC4X (Incubating) 0.1.0 RC2 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. +1 I've got some questions (see other-thread) but nothing that would invalidate the RC. Stefan
