-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> 1. Make plan. 2. Ask limited group for sanity check. 3. Code, code > code. Go back to 2. if necessary. Continue to 4. when "done". 4. > Ask larger group for sanity check and testing. Go back to 3. if > necessary. Continue to 5. when "done". 5. Release. > We're still at 1., and while I think that the problem to 1. can be > established and thought out via email, perhaps the stakeholders > need to brainstorm and research more about 1. on the lists, as this > topic has been brought up a few times already (see the ports@ and > hackers@ archives in particular). We (at least I) have done a good amount of background research but several key issues where not answered thus my public questions. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHYxyKzIOMjAek4JIRAohzAJ93pnk01isO8YJ4wvXowkvG56DkdwCgmdgS gsx4EyT8gJka/10p1Zdjtlc= =rUS6 -----END PGP SIGNATURE----- _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
