+1 Not much more to say đ
I think it is important that we include our minor fixes into a release and then go a step further with the 0.6 RC. Greetings Matthias Matthias Strljic, M.Sc. Universität Stuttgart Institut fĂźr Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW) SeidenstraĂe 36 70174 Stuttgart GERMANY Tel: +49 711 685-84530 Fax: +49 711 685-74530 E-Mail: matthias.strl...@isw.uni-stuttgart.de Web: http://www.isw.uni-stuttgart.de -----UrsprĂźngliche Nachricht----- Von: Julian Feinauer <j.feina...@pragmaticminds.de> Gesendet: Thursday, January 2, 2020 3:34 PM An: dev@plc4x.apache.org Betreff: The release train is coming (tschuuu, tschuuu) 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
