Tim Peters wrote:
Worrying about patch management mechanism, while more patches pile up and are ignored in the meantime, is not going to help and will just results in continued stagnation.
At an all-hands PythonLabs group mtg today, it was decided to move patch activity to SourceForge and kill the patches list. I'll send more about that later. There is absolutely nothing new stopping checkins while the move to the SourceForge patch manager is in progress, so if the patches continue to pile up it's certainly not the move's fault. If the pythonrun.c patch is still sitting untouched after the move, I'll assign it to you <0.7 wink>.
But how are we going to discuss new patches from people outside python-dev then ? I do see the use of moving patch submission to SourceForge, but posting the patches on the list for revision by everyone who listens is certainly better than having to scan the patch manager entries... (push strategies usually produce more feedback than pull ones).
A gateway from the patch manager to the patches list would solve this nicely.