Hi :) At the development IRC meeting of 6 April 2022 it was discussed what could be done to help large developments better move forward using the recent experience with recalls patches (bug 19532). Here is what came out of it: - resist scope creep and ask only for necessary changes for inclusion (Minimun Viable Product) - ask to focus discussions on concrete actions for the dev to reach an acceptable MVP - note somewhere all the potential follow ups ideas so that they don't get lost and it easier to move on knowing they are somewhere not lost - bring the development as a topic in meetings and QA team discussions to get focus on it What do you think of these? Any other ideas/guidelines to complete this? What are the large patch submissions that are stuck that you know about? If you could send messages in the past in the ticket, what would you sent that would have hopefully helped it move forward? Here are some other ideas: - When submitting large changes, submit a minimal version first if possible and if a more complete version might be too much. Even if it will be hard to maintain a separate more complete version for your customers. If it gets stuck, it will be worse than doing it in chunks. - Maybe reboot a submission on a new ticket with a chopped down version if noticing you should have went for the previous guideline. - Maybe propose taking on testing complicated stuff of someone else if they do the same for your submission. It will be worth your time if it avoids being stuck for months/years with dozens of rebases on the ticket plus on your customer's Kohas due to it being a effectively a fork. Cheers, -- Victor Grousset/tuxayo