The wiki page that we're instructed to use as guidence for the package porting effort (http://ostest.central.sun.com/wiki/index.php/Package_Delivery_Project) clearly states 2 or more:
7. I-Team Code Review Do your code review in the open on http://cr.opensolaris.org. Follow the steps to test your account. Make sure you use the "# webrev -O" command to generate your webrev so the bug links will work on opensoalris.org. Have your code reviewed by at least two people and correct any coding issues. The code review should only focus on the files developed to port the code, not the open source software itself. You can also have it reviewed by the SFW community at sfwnv-discuss at opensolaris.org Mike Sullivan wrote on 08/11/09 14:35: > Andre Molyneux wrote: >> Mike Sullivan wrote: >>> >>> you need two reviewers now? usually that's reserved for release builds. >> >> I thought I did. If not, I'm happy to proceed with one. > > usually the more eyes the better, so it's certainly not a problem if > you get more than one. but only one is generally required. > as we get closer to milestone builds sometimes more than one reviewer, > or particular reviewers, or even particular rti advocates are required - > but we aren't doing that at the moment unless I've missed something. > > Mike > > _______________________________________________ > sfwnv-discuss mailing list > sfwnv-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/sfwnv-discuss
