April 15, 2008
7:18 p.m.
On Tue, Apr 15, 2008 at 9:10 PM, Barry Warsaw <barry@python.org> wrote:
Better to get a release out asap after that and let the community know that there are important fixes contained within.
Fair enough. Where's the release then?
Look, I know you folks are working hard on this, and I certainly don't dis-respect that. HOWEVER, the process flow needs some re-thinking. You should not publicly release security vulnerability details before fixes are identified for current versions. I can't imagine that you don't already know that.
-Jim P.