cvs: peardoc /en/chapters rfcs.xml /en/chapters/rfcs error-handling.xml estrict-compatibility.xml header-comments.xml orphan-packages.xml orphan-proposals.xml protected-members.xml qa-team.xml rules-on-rules.xml version-naming.xml
[email protected] ("Christian Weiske")
| Newsgroups | php.pear.doc |
|---|---|
| Message-ID | <cvscweiske1241466422@cvsserver> |
cweiske Mon May 4 19:47:02 2009 UTC
Modified files:
/peardoc/en/chapters rfcs.xml
/peardoc/en/chapters/rfcs error-handling.xml
estrict-compatibility.xml
header-comments.xml orphan-packages.xml
orphan-proposals.xml
protected-members.xml qa-team.xml
rules-on-rules.xml version-naming.xml
Log:
Give the rfcs better IDs that don't correlate with the file name, but give
better file names.
cweiske-20090504194702.txt
(text/plain, 28.3 KB)
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/rfcs.xml?r1=1.3&r2=1.4&diff_format=u
Index: peardoc/en/chapters/rfcs.xml
diff -u peardoc/en/chapters/rfcs.xml:1.3 peardoc/en/chapters/rfcs.xml:1.4
--- peardoc/en/chapters/rfcs.xml:1.3 Mon May 4 19:41:43 2009
+++ peardoc/en/chapters/rfcs.xml Mon May 4 19:47:02 2009
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding='utf-8' ?>
-<part xml:id="chapters.rfcs" xmlns="http://docbook.org/ns/docbook"
+<part xml:id="rfcs" xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
>
<info>
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/rfcs/error-handling.xml?r1=1.2&r2=1.3&diff_format=u
Index: peardoc/en/chapters/rfcs/error-handling.xml
diff -u peardoc/en/chapters/rfcs/error-handling.xml:1.2 peardoc/en/chapters/rfcs/error-handling.xml:1.3
--- peardoc/en/chapters/rfcs/error-handling.xml:1.2 Mon May 4 18:08:08 2009
+++ peardoc/en/chapters/rfcs/error-handling.xml Mon May 4 19:47:02 2009
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter version="5.0" xml:id="chapters.rfcs.error-handling"
+<chapter version="5.0" xml:id="rfc.error-handling"
xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
>
@@ -19,7 +19,7 @@
<link xlink:href="&url.pear.pepr.proposal;132">proposal #132</link>.
</para>
- <section xml:id="chapters.rfcs.error-handling.audience">
+ <section xml:id="rfc.error-handling.audience">
<title>Audience</title>
<para>This document is targeted at PHP developers writing packages for
@@ -34,7 +34,7 @@
well as pointers to other references.</para>
</section>
- <section xml:id="chapters.rfcs.error-handling.definition">
+ <section xml:id="rfc.error-handling.definition">
<title>Definition of error</title>
<para>An error is defined as an unexpected, invalid program state from
@@ -138,7 +138,7 @@
exception, logging or warning should occur.</para>
</section>
- <section xml:id="chapters.rfcs.error-handling.signalling">
+ <section xml:id="rfc.error-handling.signalling">
<title>Error Signaling in PHP5 PEAR packages</title>
<para>Error conditions in PEAR packages written for PHP5 must be signaled
@@ -262,7 +262,7 @@
</orderedlist>
</section>
- <section xml:id="chapters.rfcs.error-handling.flow">
+ <section xml:id="rfc.error-handling.flow">
<title>Exceptions and normal program flow</title>
<para>Exceptions should never be used as normal program flow. If removing
@@ -301,7 +301,7 @@
but in the example above this is simply lazy development.</para>
</section>
- <section xml:id="chapters.rfcs.error-handling.hierarchies">
+ <section xml:id="rfc.error-handling.hierarchies">
<title>Exception class hierarchies</title>
<para>All of PEAR packages exceptions must be descendant from
@@ -315,7 +315,7 @@
level exception.</para>
</section>
- <section xml:id="chapters.rfcs.error-handling.documentation">
+ <section xml:id="rfc.error-handling.documentation">
<title>Documenting Exceptions</title>
<para>Because PHP, unlike Java, does not require you to explicitly state
@@ -368,7 +368,7 @@
?></programlisting>
</section>
- <section xml:id="chapters.rfcs.error-handling.api">
+ <section xml:id="rfc.error-handling.api">
<title>Exceptions as part of the API</title>
<para>Exceptions play a critical role in the API of your library.
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/rfcs/estrict-compatibility.xml?r1=1.2&r2=1.3&diff_format=u
Index: peardoc/en/chapters/rfcs/estrict-compatibility.xml
diff -u peardoc/en/chapters/rfcs/estrict-compatibility.xml:1.2 peardoc/en/chapters/rfcs/estrict-compatibility.xml:1.3
--- peardoc/en/chapters/rfcs/estrict-compatibility.xml:1.2 Mon May 4 18:08:08 2009
+++ peardoc/en/chapters/rfcs/estrict-compatibility.xml Mon May 4 19:47:02 2009
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter version="5.0" xml:id="chapters.rfcs.estrict-compatibility"
+<chapter version="5.0" xml:id="rfc.estrict-compatibility"
xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
>
@@ -14,7 +14,7 @@
<link xlink:href="&url.pear.pepr.proposal;419">proposal #419</link>.
</para>
- <section xml:id="chapters.rfcs.estrict-compatibility.issue">
+ <section xml:id="rfc.estrict-compatibility.issue">
<title>The issue</title>
<para>First stable release of PHP version 5 was done two years ago. This
@@ -41,14 +41,14 @@
</itemizedlist>
</section>
- <section xml:id="chapters.rfcs.estrict-compatibility.solution">
+ <section xml:id="rfc.estrict-compatibility.solution">
<title>The solution</title>
<para>The proposed solution is to focus on "forward compatibility"
instead. PHP version 5 has a builtin means to ensure that code is forward
compatible, which is <token>E_STRICT</token> error reporting level.</para>
- <section xml:id="chapters.rfcs.estrict-compatibility.solution.definition">
+ <section xml:id="rfc.estrict-compatibility.solution.definition">
<title>Definition of E_STRICT-compatible package</title>
<para>The package is considered <token>E_STRICT</token>-compatible
@@ -81,7 +81,7 @@
is discouraged.</para>
</section>
- <section xml:id="chapters.rfcs.estrict-compatibility.solution.changes">
+ <section xml:id="rfc.estrict-compatibility.solution.changes">
<title>Proposed changes</title>
<para>After this RFC is accepted, a deadline for accepting the new non
@@ -129,7 +129,7 @@
</section>
</section>
- <section xml:id="chapters.rfcs.estrict-compatibility.solution.impactexisting">
+ <section xml:id="rfc.estrict-compatibility.solution.impactexisting">
<title>Impact on existing packages</title>
<para>Development and release process of existing PEAR packages which
@@ -151,7 +151,7 @@
</section>
</section>
- <section xml:id="chapters.rfcs.estrict-compatibility.notes">
+ <section xml:id="rfc.estrict-compatibility.notes">
<title>Notes</title>
<para>Several people expressed the concern that mandating
@@ -160,7 +160,7 @@
base PEAR classes to PHP5.</para>
</section>
- <section xml:id="chapters.rfcs.estrict-compatibility.changes">
+ <section xml:id="rfc.estrict-compatibility.changes">
<title>A (Non-Exhaustive) List of E_STRICT-compatibility changes</title>
<itemizedlist>
@@ -186,7 +186,7 @@
</itemizedlist>
<para>These changes obviously imply following the <link
- linkend="chapters.rfcs.error-handling">Error Handling Guidelines for PHP5
+ linkend="rfc.error-handling">Error Handling Guidelines for PHP5
packages</link> since PEAR class itself is not
<token>E_STRICT</token>-compatible.</para>
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/rfcs/header-comments.xml?r1=1.2&r2=1.3&diff_format=u
Index: peardoc/en/chapters/rfcs/header-comments.xml
diff -u peardoc/en/chapters/rfcs/header-comments.xml:1.2 peardoc/en/chapters/rfcs/header-comments.xml:1.3
--- peardoc/en/chapters/rfcs/header-comments.xml:1.2 Mon May 4 18:08:08 2009
+++ peardoc/en/chapters/rfcs/header-comments.xml Mon May 4 19:47:02 2009
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter version="5.0" xml:id="chapters.rfcs.header-comments"
+<chapter version="5.0" xml:id="rfc.header-comments"
xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:phd="http://www.php.net/ns/phd"
@@ -26,7 +26,7 @@
<link xlink:href="&url.pear.pepr.proposal;128">proposal #128</link>.
</para>
- <section xml:id="chapters.rfcs.header-comments.base">
+ <section xml:id="rfc.header-comments.base">
<title>Base docblock</title>
<para>All source code files in the PEAR repository shall contain a
@@ -56,7 +56,7 @@
* @author Another Author <[email protected]>
* @copyright 1997-2005 The PHP Group
* @license http://www.php.net/license/3_0.txt PHP License 3.0
- * @version CVS: $Id: header-comments.xml,v 1.2 2009/05/04 18:08:08 cweiske Exp $
+ * @version CVS: $Id: header-comments.xml,v 1.3 2009/05/04 19:47:02 cweiske Exp $
* @link http://pear.php.net/package/PackageName
* @see NetOther, Net_Sample::Net_Sample()
* @since File available since Release 1.2.0
@@ -88,7 +88,7 @@
?></programlisting>
</section>
- <section xml:id="chapters.rfcs.header-comments.required">
+ <section xml:id="rfc.header-comments.required">
<title>Required tags</title>
<section>
@@ -204,7 +204,7 @@
</section>
</section>
- <section xml:id="chapters.rfcs.header-comments.optional">
+ <section xml:id="rfc.header-comments.optional">
<title>Optional tags</title>
<section>
@@ -257,10 +257,10 @@
docblocks will use <literal>@package_version@</literal>, which gets
replaced with the release's version number by the PEAR installer.</para>
- <para>This seems the best compromise because <literal>$Id: header-comments.xml,v 1.2 2009/05/04 18:08:08 cweiske Exp $</literal>'s
+ <para>This seems the best compromise because <literal>$Id: header-comments.xml,v 1.3 2009/05/04 19:47:02 cweiske Exp $</literal>'s
talk about files while the release version numbers talk about the
- classes. <literal>$Id: header-comments.xml,v 1.2 2009/05/04 18:08:08 cweiske Exp $</literal> is used rather than
- <literal>$Revision: 1.2 $</literal> or other shorter tags because it is the
+ classes. <literal>$Id: header-comments.xml,v 1.3 2009/05/04 19:47:02 cweiske Exp $</literal> is used rather than
+ <literal>$Revision: 1.3 $</literal> or other shorter tags because it is the
standard and provides all of the potentially desired information.</para>
</section>
@@ -274,7 +274,7 @@
</section>
</section>
- <section xml:id="chapters.rfcs.header-comments.orderspacing">
+ <section xml:id="rfc.header-comments.orderspacing">
<title>Order and spacing</title>
<para>To ease long term readability of PEAR source code, the text and tags
@@ -282,7 +282,7 @@
standard is adopted from the JavaDoc standard.</para>
</section>
- <section xml:id="chapters.rfcs.header-comments.packageversion">
+ <section xml:id="rfc.header-comments.packageversion">
<title>@package_version@ Usage</title>
<para>There are two ways to implement the @package_version@ replacements.
@@ -311,7 +311,7 @@
);</programlisting>
</section>
- <section xml:id="chapters.rfcs.header-comments.transition">
+ <section xml:id="rfc.header-comments.transition">
<title>Transition policy</title>
<section>
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/rfcs/orphan-packages.xml?r1=1.1&r2=1.2&diff_format=u
Index: peardoc/en/chapters/rfcs/orphan-packages.xml
diff -u peardoc/en/chapters/rfcs/orphan-packages.xml:1.1 peardoc/en/chapters/rfcs/orphan-packages.xml:1.2
--- peardoc/en/chapters/rfcs/orphan-packages.xml:1.1 Mon May 4 18:35:49 2009
+++ peardoc/en/chapters/rfcs/orphan-packages.xml Mon May 4 19:47:02 2009
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter version="5.0" xml:id="chapters.rfcs.orphan-packages"
+<chapter version="5.0" xml:id="rfc.orphan-packages"
xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
>
@@ -14,7 +14,7 @@
<link xlink:href="&url.pear.pepr.proposal;192">proposal #192</link>.
</para>
- <section xml:id="chapters.rfcs.orphan-packages.problem">
+ <section xml:id="rfc.orphan-packages.problem">
<title>The Problem</title>
<para>Sometimes a package is left without care for a long time. It becomes
@@ -22,7 +22,7 @@
to step up to remedy it.</para>
</section>
- <section xml:id="chapters.rfcs.orphan-packages.whatis">
+ <section xml:id="rfc.orphan-packages.whatis">
<title>What can be considered an orphaned package?</title>
<para>The following are considered orphaned packages:</para>
@@ -52,7 +52,7 @@
</itemizedlist>
</section>
- <section xml:id="chapters.rfcs.orphan-packages.contacting">
+ <section xml:id="rfc.orphan-packages.contacting">
<title>Contact process</title>
<para>A QA core-team member tries to contact the current maintainers and
@@ -83,12 +83,12 @@
out.</para>
</section>
- <section xml:id="chapters.rfcs.orphan-packages.findlead">
+ <section xml:id="rfc.orphan-packages.findlead">
<title>Finding a new lead</title>
<para>A message will be sent to pear-dev asking for volunteers.</para>
- <section xml:id="chapters.rfcs.orphan-packages.findlead.stepup">
+ <section xml:id="rfc.orphan-packages.findlead.stepup">
<title>Somebody steps up</title>
<para>If you are willing to take over a package you must notify the QA
@@ -100,13 +100,13 @@
assign new maintainer-ship.</para>
</section>
- <section xml:id="chapters.rfcs.orphan-packages.findlead.nobody">
+ <section xml:id="rfc.orphan-packages.findlead.nobody">
<title>Nobody wishes to take over</title>
<para>A QA core team member will mark the package as orphaned.</para>
</section>
- <section xml:id="chapters.rfcs.orphan-packages.findlead.status">
+ <section xml:id="rfc.orphan-packages.findlead.status">
<title>Orphan status</title>
<para>If a package is orphaned, a warning and a call for maintainers
@@ -114,7 +114,7 @@
</section>
</section>
- <glossary xml:id="chapters.rfcs.orphan-packages.glossary">
+ <glossary xml:id="rfc.orphan-packages.glossary">
<info>
<title>Glossary</title>
</info>
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/rfcs/orphan-proposals.xml?r1=1.1&r2=1.2&diff_format=u
Index: peardoc/en/chapters/rfcs/orphan-proposals.xml
diff -u peardoc/en/chapters/rfcs/orphan-proposals.xml:1.1 peardoc/en/chapters/rfcs/orphan-proposals.xml:1.2
--- peardoc/en/chapters/rfcs/orphan-proposals.xml:1.1 Mon May 4 18:35:49 2009
+++ peardoc/en/chapters/rfcs/orphan-proposals.xml Mon May 4 19:47:02 2009
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter version="5.0" xml:id="chapters.rfcs.orphan-proposals"
+<chapter version="5.0" xml:id="rfc.orphan-proposals"
xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
>
@@ -14,7 +14,7 @@
<link xlink:href="&url.pear.pepr.proposal;188">proposal #188</link>.
</para>
- <section xml:id="chapters.rfcs.orphan-proposals.problem">
+ <section xml:id="rfc.orphan-proposals.problem">
<title>The problem</title>
<para>It happens more or less often, that</para>
@@ -31,7 +31,7 @@
</orderedlist>
</section>
- <section xml:id="chapters.rfcs.orphan-proposals.solution">
+ <section xml:id="rfc.orphan-proposals.solution">
<title>The solution</title>
<para>In these 2 cases PEAR QA should step in and try to get in touch with
@@ -41,7 +41,7 @@
<para>For these steps the following time frames are proposed:</para>
- <section xml:id="chapters.rfcs.orphan-proposals.solution.unfinished">
+ <section xml:id="rfc.orphan-proposals.solution.unfinished">
<title>For proposals in stages "draft" and "proposal"</title>
<itemizedlist>
@@ -57,7 +57,7 @@
</itemizedlist>
</section>
- <section xml:id="chapters.rfcs.orphan-proposals.solution.finished">
+ <section xml:id="rfc.orphan-proposals.solution.finished">
<title>For proposals in stage "finished"</title>
<itemizedlist>
@@ -84,7 +84,7 @@
</section>
</section>
- <section xml:id="chapters.rfcs.orphan-proposals.orphanmarker">
+ <section xml:id="rfc.orphan-proposals.orphanmarker">
<title>Orphan marker</title>
<para>Finished proposals should not be deleted, but marked as orphan. This
@@ -107,14 +107,14 @@
</itemizedlist>
</section>
- <section xml:id="chapters.rfcs.orphan-proposals.cleanup">
+ <section xml:id="rfc.orphan-proposals.cleanup">
<title>Initial cleanup</title>
<para>To get this process running, an initial cleanup is required. The
procedure is only run once, when this proposal gets accepted. This cleanup
should have the following steps:</para>
- <section xml:id="chapters.rfcs.orphan-proposals.cleanup.unfinished">
+ <section xml:id="rfc.orphan-proposals.cleanup.unfinished">
<title>Proposals in stages "proposal" and "draft"</title>
<para>PEAR QA will post a reminder comment to every proposal which shows
@@ -123,7 +123,7 @@
deleted.</para>
</section>
- <section xml:id="chapters.rfcs.orphan-proposals.cleanup.finished">
+ <section xml:id="rfc.orphan-proposals.cleanup.finished">
<title>Proposals in stage "finished"</title>
<para>PEAR QA will try to get in touch with the proposers of every
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/rfcs/protected-members.xml?r1=1.2&r2=1.3&diff_format=u
Index: peardoc/en/chapters/rfcs/protected-members.xml
diff -u peardoc/en/chapters/rfcs/protected-members.xml:1.2 peardoc/en/chapters/rfcs/protected-members.xml:1.3
--- peardoc/en/chapters/rfcs/protected-members.xml:1.2 Mon May 4 18:08:08 2009
+++ peardoc/en/chapters/rfcs/protected-members.xml Mon May 4 19:47:02 2009
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter version="5.0" xml:id="chapters.rfcs.protected-members"
+<chapter version="5.0" xml:id="rfc.protected-members"
xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
>
@@ -14,7 +14,7 @@
<link xlink:href="&url.pear.pepr.proposal;99">proposal #99</link>.
</para>
- <section xml:id="chapters.rfcs.protected-members.preface">
+ <section xml:id="rfc.protected-members.preface">
<title>Preface</title>
<para>This RFC aims to resolve whether or not protected class members will
@@ -31,7 +31,7 @@
</note>
</section>
- <section xml:id="chapters.rfcs.protected-members.voting">
+ <section xml:id="rfc.protected-members.voting">
<title>Voting</title>
<note>
@@ -46,7 +46,7 @@
class members will not be prefixed. If negative, they will be
prefixed.</para>
- <section xml:id="chapters.rfcs.protected-members.voting.noprefix">
+ <section xml:id="rfc.protected-members.voting.noprefix">
<title>No prefix (accepted)</title>
<para>A vote of <literal>+1</literal> suggests class members should not
@@ -59,7 +59,7 @@
}</programlisting>
</section>
- <section xml:id="chapters.rfcs.protected-members.voting.prefix">
+ <section xml:id="rfc.protected-members.voting.prefix">
<title>Prefix (not accepted)</title>
<para>A vote of <literal>-1</literal> suggests class members should be
@@ -73,16 +73,16 @@
</section>
</section>
- <section xml:id="chapters.rfcs.protected-members.info">
+ <section xml:id="rfc.protected-members.info">
<title>Information</title>
- <section xml:id="chapters.rfcs.protected-members.info.changes">
+ <section xml:id="rfc.protected-members.info.changes">
<title>What's changed?</title>
<para>PHP5 Introduces PPP - Private, Public and Protected.</para>
</section>
- <section xml:id="chapters.rfcs.protected-members.info.protpriv">
+ <section xml:id="rfc.protected-members.info.protpriv">
<title>What's protected and private?</title>
<para>Protected members can be accessed in classes extending the class
@@ -90,7 +90,7 @@
the class they belong to.</para>
</section>
- <section xml:id="chapters.rfcs.protected-members.info.previously">
+ <section xml:id="rfc.protected-members.info.previously">
<title>What did we use to do, and why?</title>
<para>In PHP4, both private and protected members were prefixed with an
@@ -103,7 +103,7 @@
for protected members when the class is extended by the user.</para>
</section>
- <section xml:id="chapters.rfcs.protected-members.info.ignore">
+ <section xml:id="rfc.protected-members.info.ignore">
<title>Is it possible to accidently ignore the declarations?</title>
<para>If a member is declared as protected (using the protected
@@ -125,7 +125,7 @@
"private".</para>
</section>
- <section xml:id="chapters.rfcs.protected-members.info.readability">
+ <section xml:id="rfc.protected-members.info.readability">
<title>Does prefixing enhance readability?</title>
<para>Some would argue yes, some would argue no. Most large classes
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/rfcs/qa-team.xml?r1=1.2&r2=1.3&diff_format=u
Index: peardoc/en/chapters/rfcs/qa-team.xml
diff -u peardoc/en/chapters/rfcs/qa-team.xml:1.2 peardoc/en/chapters/rfcs/qa-team.xml:1.3
--- peardoc/en/chapters/rfcs/qa-team.xml:1.2 Mon May 4 18:08:08 2009
+++ peardoc/en/chapters/rfcs/qa-team.xml Mon May 4 19:47:02 2009
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter version="5.0" xml:id="chapters.rfcs.qa-team"
+<chapter version="5.0" xml:id="rfc.qa-team"
xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
>
@@ -20,7 +20,7 @@
<link xlink:href="&url.pear.pepr.proposal;60">proposal #60</link>.
</para>
- <section xml:id="chapters.rfcs.qa-team.issues">
+ <section xml:id="rfc.qa-team.issues">
<title>Current issues</title>
<para>There is no official QA team for PEAR. There are only a few people
@@ -48,7 +48,7 @@
</orderedlist>
</section>
- <section xml:id="chapters.rfcs.qa-team.membership">
+ <section xml:id="rfc.qa-team.membership">
<title>QA team membership</title>
<section>
@@ -105,7 +105,7 @@
</section>
</section>
- <section xml:id="chapters.rfcs.qa-team.voting">
+ <section xml:id="rfc.qa-team.voting">
<title>Voting</title>
<para>All votes (except membership related votes; see above) require a
@@ -124,10 +124,10 @@
other members of the team.</para>
</section>
- <section xml:id="chapters.rfcs.qa-team.rights">
+ <section xml:id="rfc.qa-team.rights">
<title>QA rights/responsibilities</title>
- <section xml:id="chapters.rfcs.qa-team.rights.fixrelease">
+ <section xml:id="rfc.qa-team.rights.fixrelease">
<title>Fixing bugs/making releases</title>
<para>If any QA related issues are found in a package that QA has not
@@ -173,7 +173,7 @@
things.</para>
</section>
- <section xml:id="chapters.rfcs.qa-team.rights.orphan">
+ <section xml:id="rfc.qa-team.rights.orphan">
<title>Orphaned Packages</title>
<para>The QA team can use the above stated rules to determine if a
@@ -182,7 +182,7 @@
found.</para>
</section>
- <section xml:id="chapters.rfcs.qa-team.rights.deleting">
+ <section xml:id="rfc.qa-team.rights.deleting">
<title>Deleting Package releases</title>
<para>The core QA team also has the permission to delete any release
@@ -195,7 +195,7 @@
</section>
</section>
- <section xml:id="chapters.rfcs.qa-team.pearweb">
+ <section xml:id="rfc.qa-team.pearweb">
<title>pearweb QA subsection</title>
<para>It seems that there is a lack of QA material in the manual that
@@ -243,7 +243,7 @@
</section>
</section>
- <section xml:id="chapters.rfcs.qa-team.summary">
+ <section xml:id="rfc.qa-team.summary">
<title>Summary</title>
<para>QA core group access rights:</para>
@@ -302,7 +302,7 @@
</orderedlist>
</section>
- <section xml:id="chapters.rfcs.qa-team.actions">
+ <section xml:id="rfc.qa-team.actions">
<title>Actions Required if accepted</title>
<orderedlist>
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/rfcs/rules-on-rules.xml?r1=1.2&r2=1.3&diff_format=u
Index: peardoc/en/chapters/rfcs/rules-on-rules.xml
diff -u peardoc/en/chapters/rfcs/rules-on-rules.xml:1.2 peardoc/en/chapters/rfcs/rules-on-rules.xml:1.3
--- peardoc/en/chapters/rfcs/rules-on-rules.xml:1.2 Mon May 4 18:08:08 2009
+++ peardoc/en/chapters/rfcs/rules-on-rules.xml Mon May 4 19:47:02 2009
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter version="5.0" xml:id="chapters.rfcs.rules-on-rules"
+<chapter version="5.0" xml:id="rfc.rules-on-rules"
xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
>
@@ -21,7 +21,7 @@
<link xlink:href="&url.pear.pepr.proposal;39">proposal #39</link>.
</para>
- <section xml:id="chapters.rfcs.rules-on-rules.issues">
+ <section xml:id="rfc.rules-on-rules.issues">
<title>The issues</title>
<para>For PEAR to continue to grow, and encourage contributors, testers,
@@ -74,7 +74,7 @@
<para>(RFC = Request for comments) for those who are wondering..</para>
</section>
- <section xml:id="chapters.rfcs.rules-on-rules.solution">
+ <section xml:id="rfc.rules-on-rules.solution">
<title>The Proposed Solution</title>
<orderedlist>
@@ -233,7 +233,7 @@
</orderedlist>
</section>
- <section xml:id="chapters.rfcs.rules-on-rules.actions">
+ <section xml:id="rfc.rules-on-rules.actions">
<title>Actions Required if accepted</title>
<para>Changes to the PEPr proposal system:</para>
@@ -279,7 +279,7 @@
</orderedlist>
</section>
- <section xml:id="chapters.rfcs.rules-on-rules.comments">
+ <section xml:id="rfc.rules-on-rules.comments">
<title>Comments</title>
<itemizedlist>
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/rfcs/version-naming.xml?r1=1.4&r2=1.5&diff_format=u
Index: peardoc/en/chapters/rfcs/version-naming.xml
diff -u peardoc/en/chapters/rfcs/version-naming.xml:1.4 peardoc/en/chapters/rfcs/version-naming.xml:1.5
--- peardoc/en/chapters/rfcs/version-naming.xml:1.4 Mon May 4 18:08:08 2009
+++ peardoc/en/chapters/rfcs/version-naming.xml Mon May 4 19:47:02 2009
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter version="5.0" xml:id="chapters.rfcs.version-naming"
+<chapter version="5.0" xml:id="rfc.version-naming"
xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
>
@@ -16,7 +16,7 @@
not be reached on the version naming standard, below is the proposed
replacement RFC, which attempts to address the issues.</para>
- <section xml:id="chapters.rfcs.version-naming.issue">
+ <section xml:id="rfc.version-naming.issue">
<title>The issue</title>
<para>Pear-group announced a versioning naming standard which unfortunatly
@@ -58,7 +58,7 @@
filename, output when installing a package.</para>
</section>
- <section xml:id="chapters.rfcs.version-naming.standard">
+ <section xml:id="rfc.version-naming.standard">
<title>New version naming standard</title>
<para>The solution is to replace the existing standard with one a
@@ -150,7 +150,7 @@
</tgroup>
</table>
- <section xml:id="chapters.rfcs.version-naming.standard.bcbreaks">
+ <section xml:id="rfc.version-naming.standard.bcbreaks">
<title>Deliberatly Breaking BC on packages</title>
<para>Breaking BC may only be done:</para>
@@ -167,7 +167,7 @@
</itemizedlist>
</section>
- <section xml:id="chapters.rfcs.version-naming.standard.first">
+ <section xml:id="rfc.version-naming.standard.first">
<title>First Releases</title>
<itemizedlist>
@@ -182,7 +182,7 @@
</itemizedlist>
</section>
- <section xml:id="chapters.rfcs.version-naming.standard.bugfix">
+ <section xml:id="rfc.version-naming.standard.bugfix">
<title>Bug fix only Releases</title>
<itemizedlist>
@@ -222,7 +222,7 @@
</itemizedlist>
</section>
- <section xml:id="chapters.rfcs.version-naming.standard.feature">
+ <section xml:id="rfc.version-naming.standard.feature">
<title>Feature addition Releases (that may also include bug
fixes)</title>
@@ -245,7 +245,7 @@
</itemizedlist>
</section>
- <section xml:id="chapters.rfcs.version-naming.standard.stable">
+ <section xml:id="rfc.version-naming.standard.stable">
<title>Stable Releases</title>
<para>You should never release stable packages with a
@@ -253,7 +253,7 @@
and is the only significant change that is being proposed.)</para>
</section>
- <section xml:id="chapters.rfcs.version-naming.standard.rc">
+ <section xml:id="rfc.version-naming.standard.rc">
<title>Appending RC releases (Release Candidates)</title>
<para>RC releases are strongly recommended for larger, popular
@@ -284,7 +284,7 @@
</itemizedlist>
</section>
- <section xml:id="chapters.rfcs.version-naming.standard.defbcbreaks">
+ <section xml:id="rfc.version-naming.standard.defbcbreaks">
<title>Defining BC breaks</title>
<para>At present this is left to the maintainer to define (using common