diff options
Diffstat (limited to 'zh_TW.Big5/articles/pr-guidelines/article.xml')
| -rw-r--r-- | zh_TW.Big5/articles/pr-guidelines/article.xml | 70 |
1 files changed, 29 insertions, 41 deletions
diff --git a/zh_TW.Big5/articles/pr-guidelines/article.xml b/zh_TW.Big5/articles/pr-guidelines/article.xml index 9018f4bfa9..420c2aff87 100644 --- a/zh_TW.Big5/articles/pr-guidelines/article.xml +++ b/zh_TW.Big5/articles/pr-guidelines/article.xml @@ -1,10 +1,6 @@ <?xml version="1.0" encoding="big5"?> -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN" - "../../../share/xml/freebsd45.dtd" [ -<!ENTITY man.edit-pr.1 "<citerefentry><refentrytitle>edit-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>"> -<!ENTITY man.query-pr.1 "<citerefentry><refentrytitle>query-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>"> -]> - +<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN" + "../../../share/xml/freebsd50.dtd"> <!-- $FreeBSD$ --> <!-- The FreeBSD Documentation Project --> <!-- Translate into Chinese by chinsan.tw@gmail.com --> @@ -13,15 +9,14 @@ 問題回報(PR)的處理原則 The FreeBSD Project - http://www.FreeBSD.org --> - -<article lang='zh_tw'> +<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="zh_tw"> <!-- :START of Article Metadata --> - <articleinfo> - <title>問題回報(PR)的處理原則</title> + <info><title>問題回報(PR)的處理原則</title> + <pubdate>$FreeBSD$</pubdate> - <legalnotice id="trademarks" role="trademarks"> + <legalnotice xml:id="trademarks" role="trademarks"> &tm-attrib.freebsd; &tm-attrib.opengroup; &tm-attrib.general; @@ -33,22 +28,16 @@ </abstract> <authorgroup> - <author> - <firstname>Dag-Erling</firstname> - <surname>Smørgrav</surname> - </author> - - <author> - <firstname>Hiten</firstname> - <surname>Pandya</surname> - </author> + <author><personname><firstname>Dag-Erling</firstname><surname>Smørgrav</surname></personname></author> + + <author><personname><firstname>Hiten</firstname><surname>Pandya</surname></personname></author> </authorgroup> <releaseinfo>$FreeBSD$</releaseinfo> - </articleinfo> + </info> <!-- :END of Article Metadata--> - <section id="intro"> + <section xml:id="intro"> <title>前言</title> <para>GNATS 是 FReeBSD 計劃所採用的一套專門管理錯誤(回報bug) 系統。 @@ -59,7 +48,7 @@ to the wider community. 為了讓 GNATS 資料庫使用上儘量一致，於是就產生了怎麼處理像是：followup(回文)、關閉PR等的參考原則。</para> </section> - <section id="pr-lifecycle"> + <section xml:id="pr-lifecycle"> <title>問題回報(PR)的生命週期</title> <itemizedlist> @@ -115,7 +104,7 @@ </note> </section> - <section id="pr-states"> + <section xml:id="pr-states"> <title>問題回報(PR)的狀態</title> <para>若 PR 有任何變化的話，請務必記得更新 PR 的『狀態(state)』。 @@ -191,7 +180,7 @@ </note> </section> - <section id="pr-types"> + <section xml:id="pr-types"> <title>問題回報(PR)的種類</title> <para>While handling problem reports, either as a developer who has @@ -222,7 +211,7 @@ PRs is used for, when a PR belongs to one of these types, and what treatment each different type receives.</para> - <section id="pr-unassigned"> + <section xml:id="pr-unassigned"> <title>Unassigned PRs</title> <para>When PRs arrive, they are initially assigned to a generic @@ -232,7 +221,7 @@ specific &os; mailing list. Here is the current list, with the most common ones listed first:</para> - <table id="default-assignees-common"> + <table xml:id="default-assignees-common"> <title>Default Assignees — most common</title> <tgroup cols="3"> <thead> @@ -277,7 +266,7 @@ </tgroup> </table> - <table id="default-assignees-other"> + <table xml:id="default-assignees-other"> <title>Default Assignees — other</title> <tgroup cols="3"> <thead> @@ -343,7 +332,7 @@ <emphasis>aliases</emphasis>, not mailing lists.</para> </note> - <table id="common-assignees-base"> + <table xml:id="common-assignees-base"> <title>Common Assignees — base system</title> <tgroup cols="3"> <thead> @@ -470,7 +459,7 @@ </tgroup> </table> - <table id="common-assignees-ports"> + <table xml:id="common-assignees-ports"> <title>Common Assignees — Ports Collection</title> <tgroup cols="3"> <thead> @@ -568,7 +557,7 @@ </section> - <section id="pr-assigned"> + <section xml:id="pr-assigned"> <title>Assigned PRs</title> <para>If a PR has the <literal>responsible</literal> field set @@ -584,7 +573,7 @@ you please.</para> </section> - <section id="pr-dups"> + <section xml:id="pr-dups"> <title>重複的 PR</title> <para>If you find more than one PR that describe the same issue, @@ -596,7 +585,7 @@ the other PRs (which are now completely superseded).</para> </section> - <section id="pr-stale"> + <section xml:id="pr-stale"> <title>Stale PRs</title> <para>A PR is considered stale if it has not been modified in more @@ -648,7 +637,7 @@ </itemizedlist> </section> - <section id="pr-misfiled"> + <section xml:id="pr-misfiled"> <title>Misfiled PRs</title> <para>GNATS is picky about the format of a submitted bug report. @@ -714,7 +703,7 @@ </listitem> </itemizedlist> - <section id="pr-misfiled-followups"> + <section xml:id="pr-misfiled-followups"> <title>Followups misfiled as new PRs</title> <para>The first category of misfiled PRs, the one with the wrong @@ -779,7 +768,7 @@ This was misfiled because the subject did not have the format: avoid the next time a followup to an existing PR is sent.</para> </section> - <section id="pr-misfiled-format"> + <section xml:id="pr-misfiled-format"> <title>PRs misfiled because of missing fields</title> <para>The second type of misfiled PRs is usually the result of a @@ -802,7 +791,7 @@ This was misfiled because the subject did not have the format: PR, but it is relatively easy to do most of the time.</para> </section> - <section id="pr-misfiled-notpr"> + <section xml:id="pr-misfiled-notpr"> <title>Misfiled PRs that are not really problem reports</title> <para>Sometimes a user wants to submit a report for a problem @@ -871,16 +860,15 @@ This was misfiled because the subject did not have the format: </section> </section> - <section id="references"> + <section xml:id="references"> <title>延伸閱讀</title> <para>下面這是在寫、處理 PR 時，可以參考的資料。當然很明顯，這份清單仍須補充。</para> <itemizedlist> <listitem> - <para><ulink - url="&url.articles.problem-reports;/article.html">How to - Write FreeBSD Problem Reports</ulink>—給 PR 回報者用的參考原則。</para> + <para><link xlink:href="&url.articles.problem-reports;/article.html">How to + Write FreeBSD Problem Reports</link>—給 PR 回報者用的參考原則。</para> </listitem> </itemizedlist> </section> |