No subject

the code and do a +1 from
reviewing, alongside one non-core person that does the same.

The texts could go something like this, but this is only a draft for 
improvement:

- Two positive votes by doing testing of the code against the 
version-branches submitted in the original RFC (one of them made by a 
core developer)

It could be elaborated later, that if the branches for what the code 
will eventually be committed for, have changed after the initial RFC 
submit, only those branches is required testing against.

I don't know what is meant by the "functionality" sentence, so it is 
kinda hard to improve on ;)

-- 
Lars Houmark
Member of the TYPO3 Security Team