I _think_ the deken update won't break anything (after all you don't have to use it to run Pd) - so I think it's worth the risk of updating it.
Also, the GUI changes would be hard to untangle from the other updates, so I think the safer thing is to just leave them in. As far as I can tell they're adequately shaken down now.
Even though it's not considered correct behavior, I still find it less problematic to fully commit to changes in the main branch than to try to maintain long twisted chains of duplicate bugfixes in both master and in some 0.52 branch - this didn't work out so well this time around (I cornered myself into taking the GUI updates into a minor release) but, ouch, we all just have to deal with my 1970s-vintage coding skills :)
M
On Fri, Oct 14, 2022 at 05:18:58PM +0200, IOhannes m zmölnig wrote:
Am 14. Oktober 2022 17:12:02 MESZ schrieb "IOhannes m zmölnig" zmoelnig@iem.at:
Speaking of which: I think a bugfix release 0.52.3 should probably *not* contain the "rework of the interface to GUI", which is a rather big change...
Also I see that my deken update branch has been merged, which is great. But it includes mostly new features, rather than just bugfixes.
So are we aiming at 0.53.0 or at 0.52.3?
mfg.sfg.jfd IOhannes
Pd-dev mailing list Pd-dev@lists.iem.at https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-dev__;!!...