Making a separate item for each merge is insane.
Please don't do this.
When you check in, use the Item numbers for the issues that were fixed on TWiki 4 branch.
If necessary we can relax the constraint that requires bug items to be in an open state, for DEVELOP branch.
It is also not very helpful to have simply a revision number as log message - better suggestion is to re-use some of the original commit message(s).
(I don't mind a merge declaration with original rev numbers, but a human readable log message on change committed is first priority).
I was just going through the rather large volume of mail, doing a basic single-rev merge of any changes that didn't result in a conflict. The original rev number is sufficient to connect the develop update with the original update and duplicating the log message seemed unnecessarily time consuming. Even doing this much took more time and energy than I have to spare, but I wanted to help out.
It would seem to make more sense for someone to write a script to do the labour, but if that can't be done or for some reason isn't desirable, I'll leave the task to someone who is willing to put in the large amount of manual effort involved.
Obviously CDot and I didn't talk enough about what he meant by merging TWiki 4 changes into develop. Sorry about that, Cdot.