At club we discussed how much the testing branch deviates from stable during each development cycle. This topic allows us to understand why this happens and discuss how to reduce the impact of it
A while ago we moved towards a more frequent update of stable with more structure in the change process but this point in time sees us in a particularly significant period of change. The core Zynthian code is being rationalised and significant changes to UI to improve workflow. Testing needs to be bleeding edge for a while longer than we would ideally like. @jofemodo is doing far more hot-fixes to stable during this development cycle. We are also learning valuable lessons about user experience, documentation, etc. just like the subject of this discussion.
I think we should introduce a testing branch of documentation / wiki. This works allow me behaviour to be documented and that documentation be tested.
It may be appropriate to agree goals for each development cycle so that we know when it is finished and can merge into stable. That may also allow consideration of how much change is appropriate during a cycle.