plc4x-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julian Feinauer <>
Subject AW: Preparation of Release 0.3.1
Date Thu, 28 Feb 2019 13:33:41 GMT
Cool... I'll take care of that

Von meinem Mobiltelefon gesendet

-------- Urspr├╝ngliche Nachricht --------
Betreff: Re: Preparation of Release 0.3.1
Von: Christofer Dutz


´╗┐Am 28.02.19, 14:25 schrieb "Tim Mitsch" <>:

    Hey guys

    Sorry that has been my fault ... i fixed that issue but did not resolved the jira ticket.
    I have done that just few minutes ago with relation the regarding commit.

    So from my side we could start for preparing 0.3.1 RC


    Am 28.02.19, 12:33 schrieb "Christofer Dutz" <>:

        Cause that would have been the last open S7 bug that's been reported and is still


        Am 28.02.19, 12:33 schrieb "Christofer Dutz" <>:

            Not quite sure, if we should also have a look at:
            PLC4X-78 Write operations seem to fail

            Am 28.02.19, 12:03 schrieb "Julian Feinauer" <>:

                Thanks Chris,

                @tim: Can you clarify or give your feedback about PLC4X-83?


                Von: Christofer Dutz <>
                Gesendet: Donnerstag, 28. Februar 2019 11:27:17
                Betreff: Re: Preparation of Release 0.3.1

                Hi Julian,

                I thought Tim had fixed that ... as he did that I didn't want to close it
as this way I would have been the person who resolved it ;-)


                Am 28.02.19, 10:19 schrieb "Julian Feinauer" <>:


                    did anyone do any further checks for our planned release 0.3.1.

                    The two TIckets PLC4X-82 and PLC4X-84 are marked as done but PLC4X-83
(When requesting an odd number of bytes in payload the fill-byte is not handled correctly)
is still open.

                    @cdutz, @tim

                    Both of you did most of the work... can you give an update?

                    I would like to end this soon and prepare an RC.



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message