Hi, I think the proposal seems excellent.
I am working on the Netty-based S7 driver for the reception of alarms and notifications from the PLC. I understand that it is a Legacy code but serves as a reference for the MSPEC implementation. I take this opportunity to wish you all an excellent 2020, Best regards El jue., 2 de enero de 2020 10:33 a. m., Julian Feinauer < [email protected]> escribió: > Hi folks, > > I just had a private Chat with Chris about the next steps and I think its > time again to prepare a release / releases. > As we have discussed multiple times, with the (a bit breaking) refactoring > we want to jump on a new minor version 0.6 but also release all the fixes > that have been done in the current codebase (which we want to keep alive > for sometime) as rel/0.5 branch, basically. > > So I suggest to prepare a release 0.5.1 for the current version of the > develop (0.5 release + all PRs we got there) and then point the develop to > the “next-gen” branch and clean this up for a release 0.6.0 which has LESS > drivers but especially the new (mostly generated) S7 Driver. > > So short TL;DR: > > * Release current develop as 0.5.1 > * Current develop -> rel/0.5 > * Next-gen branch -> develop > * Prepare a release 0.6.0 with the new s7 driver and without the old > one > * Continue Development in develop (0.6.x) but also maintain (for some > time) rel/0.5 for compatibility > > Is this clear and understandable? And if so, does anyone agree or do we > have any controversy we should discuss in more details? > > Julian >
