I agree with this
On May 18, 2025, at 3:17 PM, Christof Ressi info@christofressi.com wrote:
Hi,
thanks for clarifying!
Then I go through PRs and bug reports, fixing what I can and adopting whatever looks like it won't slow me down too much. (I really should read all the PRs line by line but if I tried to do that there would never be another release again). This often takes a week or so.
Here's the thing: if you announce this "merge window" in advance, we can give you a list of prioritized PRs and also make sure they are in good shape. Then you wouldn't have to go through all PRs yourself. In fact, that's what you did last time with Pd 0.55 (after I complained the previous time :) and I found it really helpful!
Again, keep in mind that some us might be in the final stages of a project, be on vacation or have a sick child at home. (In my case, the chance for one of these things to be true is rather high at the moment.) If we miss this one week merge window for feature PRs, it usually means we have to wait for another whole year...
I agree with this. If we know the general milestones for the next release, we can focus on which PRs are already "far enough along" to try test/merge or bring your attention to regarding design, API, etc. I know for the bigger work, we have tried to do this early enough in stages that it's ready to go by the time the development window starts (soundfile and net objects updates), however like Christof, I can't always jump in quickly.
-------- Dan Wilcox danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/