- 04/24/2011 12:23:13 PM (4 years ago)
v5 v6 16 16 17 17 1. File a ticket which does not describe the issue and simply says 'security issue, description pending' and has the 'security' keyword. 18 1. When the ticket goes into review, don't attach a patch or SVN branch, but put the code into a bzr branch in your home directory on svn.twistedmatrix.com. In lieu of a ticket description, the branch should of course contain a NEWS file that explains the issue and the resolution clearly. 18 1. When the ticket goes into review, don't attach a patch or SVN branch, but put the code into a bzr branch in your home directory on svn.twistedmatrix.com. 19 19 1. Mark the ticket for review as usual. Point to the location of the branch (which only committers will be able to read). 20 20 1. Review comments will be relayed outside of the issue tracker, via email. Remove the ''review'' keyword as usual, but only comment that feedback has been sent to the developer.