3. °ÝÃD¦^³ø(PR)ªºª¬ºA

­Y PR ¦³¥ô¦óÅܤƪº¸Ü¡A½Ð°È¥²°O±o§ó·s PR ªº¡yª¬ºA(state)¡z¡C ¡yª¬ºA¡zÀ³¸Ó­n¯à¥¿½T¤Ï¬M¸Ó PR ªº¥Ø«e¶i«×¤~¬O¡C

Example 1. ¥H¤U¬O§ó§ï PR ª¬ºAªº¤p¨Ò¤l¡G

·í¦³¥i¥H­×¥¿°ÝÃDªº PR ¥X²{¡A¦Ó¬ÛÃö­t³dªº developer(s) ¤]ı±o³o¼Ëªº­×¥¿¥i¥H±µ¨ü¡A¥L­Ì·| followup ¸Ó PR¡A¨Ã±N¨äª¬ºA§ï¬° ¡§feedback¡¨¡C¦P®É¡A¦^³øªÌÀ³­«·sµû¦ô³Ì²×ªº­×¥¿µ²ªG¡A¨Ã¦^À³¡G©Ò¦^³øªº¿ù»~¬O§_¤w¦¨¥\­×¥¿¡C

¨C¥÷ PR ³q±`·|¦³¤U­±³o´XºØª¬ºA¤§¤@¡G

open

PR ³Ìªìªºª¬ºA¡G³o­Ó°ÝÃD³Q´£¥X¨Ó¡A¨Ã¦bµ¥«Ý³B²z¤¤¡C

analyzed

¤w¸g¶}©l³B²z³o°ÝÃD¡A¨Ã¥B¦³§ä¨ìºÃ¦ü¸Ñ¨Mªº¤èªk¡C

feedback

»Ý­n¦^³øªÌ´£¨Ñ§ó¸Ô²Óªº¬ÛÃö¸ê®Æ¡A¥¿¦p±Ð¾Ç­n¦]§÷¬I±Ð¡Aªv¯f¤]­n¦]¤H¤UÃÄ¡A¶V¦h¬ÛÃö°T®§¡A¤~¯à¦³³Ì¨Î®ÄªG¡C

patched

¤w¸g°e¬ÛÃö patch ¤F¡A¦ý¤´¦]¬Y¨Ç­ì¦](MFC¡A©Î¨Ó¦Û¦^³øªÌªº½T»{µ²ªG²§±`)¦]¦¹©|¥¼§¹²¦¡C

suspended(¼È½w)

¦]¬°¨Sªþ¤W¬ÛÃö°T®§©Î°Ñ¦Ò¸ê®Æ¡A©Ò¥HÁÙ¨S¿ìªk³B²z³o°ÝÃD¡C This is a prime candidate for somebody who is looking for a project to take on. If the problem cannot be solved at all, it will be closed, rather than suspended. The documentation project uses ¡§suspended¡¨ for ¡§wish-list¡¨ items that entail a significant amount of work which no one currently has time for.

closed

A problem report is closed when any changes have been integrated, documented, and tested, or when fixing the problem is abandoned.

Note: The ¡§patched¡¨ state is directly related to feedback, so you may go directly to ¡§closed¡¨ state if the originator cannot test the patch, and it works in your own testing.

¥»¤å¤Î¨ä¥L¤å¥ó¡A¥i¥Ñ¦¹¤U¸ü¡Gftp://ftp.FreeBSD.org/pub/FreeBSD/doc/¡C

­Y¦³ FreeBSD ¤è­±ºÃ°Ý¡A½Ð¥ý¾\Ū FreeBSD ¬ÛÃö¤å¥ó¡A¦p¤£¯à¸Ñ¨Mªº¸Ü¡A¦A¬¢¸ß <questions@FreeBSD.org>¡C
Ãö©ó¥»¤å¥óªº°ÝÃD¡A½Ð¬¢¸ß <doc@FreeBSD.org>¡C