Thanks ! This feels a bit hard for me to be on the receiving hand, so here are some advice to get things going smoother:
- Use draft marker until the topic is mature enough to be merged. This makes the status clearer with reviewer and ultimately saves time. - Open PRs after local hardenning. Stuff opened on github needs to be of good quality - Favor small unit of works. Always moving behemoths are longer to merge. Sometime merging something good-but-not-perfect-that-will-be-improved-next-pr is a better stategy. - Keep the git history clean. 27 commits is a smell. Commit history tells a story and we do not want it to be messy. - Keep things at human pace, at human size. I'll have a round on the opened PRs. Cheers, -- Best regards, Benoit TELLIER General manager of Linagora VIETNAM. Product owner for Twake-Mail product. Chairman of the Apache James project. Mail: [email protected] Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal) Le sept. 25, 2026 7:15 PM, de Ilya Terskov <[email protected]>Hi guys one more time! Anyways builds looks stable i want them be perfect, so if you have time have a look at: Artemis github.com/apache/james-project/pull/3194 File Blob Storage github.com/apache/james-project/pull/3197 IMAP IDLE github.com/apache/james-project/pull/3198 Thanks anyone! Sorry about this hell in 3198.
