I agree. It's fine developing new features on develop as long as they are not breaking the build or have a regression. So in case of plc4py this is completely fine as this is a T-0 implementation.
- Sebastian On 2022/04/07 11:08:36 Christofer Dutz wrote: > Hi all, > > We have an always growing number of branches where things have been begun, > but never finished (Or at least never been taken back to develop) > Now some of the branches are so old, that rebasing them is not really > possible anymore. > > Could you please have a look at the branches you created, if they are still > valid, please update/rebase them. If they are obsolete, delete them. If they > contain things develop needs, please port them to develop. > > Especially for the PLC4Py work, I would feel more comfortable with this > development being done on "develop" (Similar to PLC4Net) ... only this way do > we have it on our radar when working on things. I don't want to waste your > time and effort. I do think that people understand that the different parts > of PLC4X have different maturities and having a not yet fully functional > PLC4Py is nothing to be ashamed of. > > What do you folks think? > > Chris >
