Hi, Release 0.8 sounds like a plan.
I don't have anything specific that I would want to be added, but would be in favour of a short freeze beforehand to give people a chance to test everything. Kind Regards Ben On Wed, Oct 28, 2020 at 12:24 PM Lukas Ott <[email protected]> wrote: > Hi Chris, > > +1 for bundling the next release with so many improvements and features > from Ben, Lukasz and you that it is time to put it out there for everyone > to test and see. > > For the Go part it only seems to be logical to put in as well. Especially > because we have a working Modbus implementation. We could add a remark that > Go is currently an Alpha Version and not yet battle tested if someone want > to use it in production. > This is really unlikely, so in my humble opinion we should put it out there > and see what happens. Would be awesome to attract some Go Developers to try > out PLC4Go :-) > > > Regards, > Lukas > > Am Mi., 28. Okt. 2020 um 16:30 Uhr schrieb Christofer Dutz < > [email protected]>: > > > Hi all, > > > > Having a look at the latest download stats, most people seem to be using > > 0.7.0 and I know this version has a number of issues. We should > concentrate > > on finishing what we’re working on and ship 0.8.0. > > > > I would like to finish the refactoring of the field handlers that I’ve > > been working on lately and then I’d like to merge these changes back to > > develop. > > > > Also would I like to release the modbus PLC4Go driver with the 0.8.0 … > > This way we have something people could use and experiment with and give > us > > feedback on the API. > > > > In order to do so, I however would need to move PLC4go out of the > sandbox. > > The reason for this is, that in go, if you reference dependencies, you > > don’t reference binaries, but source-code repos (mainly github) > > > > So go would reference the plc4x github repo, a given tag in the git repo > > and then append a path to that … if we move plc4go afterwards, this will > > break any application built with a previous version. I’d like to avoid > that. > > > > What are your thoughts on this? > > > > Chris > > > > >
