Skip to content

bugzilla
bugzilla
Commit 804416d9 authored by jake%bugzilla.org's avatar jake%bugzilla.org
Browse files
Options

Update links to tldp.org and Bugzilla version numbers. Also, added some text ab

out this being a development version of the guide and instructions on what to ch ange for a release (including how to disable the devel text).
parent 0f4cc7ee
Hide whitespace changes
Inline Side-by-side
Showing with 82 additions and 44 deletions
docs/sgml/Bugzilla-Guide.sgml
View file @ 804416d9
......@@ -19,12 +19,25 @@
<!ENTITY introduction SYSTEM "introduction.sgml">
<!ENTITY revhistory SYSTEM "revhistory.sgml">
<!-- Things to change for a stable release:
* bz-ver to current stable
* bz-nexver to next stable
* bz-date to the release date
* bz-devel to "IGNORE"
- COMPILE DOCS AND CHECKIN -
Also, tag and tarball at before completing
* bz-ver to devel version
* bz-devel to "INCLUDE"
For a devel release, simple bump bz-ver and bz-date
-->
<!ENTITY bz-ver "2.17.3">
<!ENTITY bz-nextver "2.18">
<!ENTITY bz-date "2003-01-02">
<!ENTITY % bz-devel "INCLUDE">
<!ENTITY bz "http://www.bugzilla.org/">
<!ENTITY bz-ver "2.16">
<!ENTITY bz-cvs-ver "2.17">
<!ENTITY bzg-date "April 2nd, 2002">
<!ENTITY bzg-ver "2.16">
<!ENTITY bzg-cvs-ver "2.17.0">
<!ENTITY bzg-auth "The Bugzilla Team">
<!ENTITY bzg-bugs "<ulink url='http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&amp;component=Documentation'>Bugzilla</ulink>">
<!ENTITY mysql "http://www.mysql.com/">
......@@ -63,7 +76,7 @@
The warning, "DTDDECL catalog types not supported" is normal.
* Try to index important terms wherever possible.
* Use "glossterm" whenever you introduce a new term.
* Follow coding standards at http://www.linuxdoc.org, and
* Follow coding standards at http://www.tldp.org, and
check out the KDE guidelines (they are nice, too)
http://i18n.kde.org/doc/markup.html
* All tags should be lowercase (needsfix)
......@@ -94,6 +107,8 @@ try to avoid clutter and feel free to waste space in the code to make it more re
</author>
</authorgroup>
<pubdate>&bz-date;</pubdate>
<abstract>
<para>
This is the documentation for Bugzilla, the mozilla.org
......@@ -109,6 +124,12 @@ try to avoid clutter and feel free to waste space in the code to make it more re
to a bug filed in
<ulink url="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&amp;component=Documentation">mozilla.org's Bugzilla</ulink>.
</para>
<![%bz-devel;[
<para>This is a development version of this guide. Information in it
is subject to change before the &bz-nextver; release of this guide
(which will correspond with the &bz-nextver; release of Bugzilla).
</para>
]]>
</abstract>
<keywordset>
......
docs/sgml/about.sgml
View file @ 804416d9
......@@ -79,29 +79,27 @@
<section id="newversions">
<title>New Versions</title>
<para>
This is the &bzg-ver; version of The Bugzilla Guide. It is so named
to match the current version of Bugzilla. If you are
This is the &bz-ver; version of The Bugzilla Guide. It is so named
to match the current version of Bugzilla.
<![%bz-devel;[
This version of the guide, like its associated Bugzilla version is a
development version. Information is subject to change between now and
when &bz-nextver; is released.
]]>
If you are
reading this from any source other than those below, please
check one of these mirrors to make sure you are reading an
up-to-date version of the Guide.
</para>
<para>
This document can be found in the following places:
The newest version of this guide can always be found at <ulink
url="http://www.bugzilla.org">bugzilla.org</ulink>; including
documentation for past releases and the current development version.
</para>
<para>
<itemizedlist>
<listitem>
<para>
<ulink url="http://www.bugzilla.org/">bugzilla.org</ulink>
</para>
</listitem>
<listitem>
<para>
<ulink url="http://www.linuxdoc.org/">The Linux
Documentation Project</ulink>
</para>
</listitem>
</itemizedlist>
The documentation for the most recent stable release of Bugzilla can also
be found at
<ulink url="http://www.tldp.org">The Linux Documentation Project</ulink>.
</para>
<para>
The latest version of this document can always be checked out via CVS.
......
docs/xml/Bugzilla-Guide.xml
View file @ 804416d9
......@@ -19,12 +19,25 @@
<!ENTITY introduction SYSTEM "introduction.sgml">
<!ENTITY revhistory SYSTEM "revhistory.sgml">
<!-- Things to change for a stable release:
* bz-ver to current stable
* bz-nexver to next stable
* bz-date to the release date
* bz-devel to "IGNORE"
- COMPILE DOCS AND CHECKIN -
Also, tag and tarball at before completing
* bz-ver to devel version
* bz-devel to "INCLUDE"
For a devel release, simple bump bz-ver and bz-date
-->
<!ENTITY bz-ver "2.17.3">
<!ENTITY bz-nextver "2.18">
<!ENTITY bz-date "2003-01-02">
<!ENTITY % bz-devel "INCLUDE">
<!ENTITY bz "http://www.bugzilla.org/">
<!ENTITY bz-ver "2.16">
<!ENTITY bz-cvs-ver "2.17">
<!ENTITY bzg-date "April 2nd, 2002">
<!ENTITY bzg-ver "2.16">
<!ENTITY bzg-cvs-ver "2.17.0">
<!ENTITY bzg-auth "The Bugzilla Team">
<!ENTITY bzg-bugs "<ulink url='http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&amp;component=Documentation'>Bugzilla</ulink>">
<!ENTITY mysql "http://www.mysql.com/">
......@@ -63,7 +76,7 @@
The warning, "DTDDECL catalog types not supported" is normal.
* Try to index important terms wherever possible.
* Use "glossterm" whenever you introduce a new term.
* Follow coding standards at http://www.linuxdoc.org, and
* Follow coding standards at http://www.tldp.org, and
check out the KDE guidelines (they are nice, too)
http://i18n.kde.org/doc/markup.html
* All tags should be lowercase (needsfix)
......@@ -94,6 +107,8 @@ try to avoid clutter and feel free to waste space in the code to make it more re
</author>
</authorgroup>
<pubdate>&bz-date;</pubdate>
<abstract>
<para>
This is the documentation for Bugzilla, the mozilla.org
......@@ -109,6 +124,12 @@ try to avoid clutter and feel free to waste space in the code to make it more re
to a bug filed in
<ulink url="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&amp;component=Documentation">mozilla.org's Bugzilla</ulink>.
</para>
<![%bz-devel;[
<para>This is a development version of this guide. Information in it
is subject to change before the &bz-nextver; release of this guide
(which will correspond with the &bz-nextver; release of Bugzilla).
</para>
]]>
</abstract>
<keywordset>
......
docs/xml/about.xml
View file @ 804416d9
......@@ -79,29 +79,27 @@
<section id="newversions">
<title>New Versions</title>
<para>
This is the &bzg-ver; version of The Bugzilla Guide. It is so named
to match the current version of Bugzilla. If you are
This is the &bz-ver; version of The Bugzilla Guide. It is so named
to match the current version of Bugzilla.
<![%bz-devel;[
This version of the guide, like its associated Bugzilla version is a
development version. Information is subject to change between now and
when &bz-nextver; is released.
]]>
If you are
reading this from any source other than those below, please
check one of these mirrors to make sure you are reading an
up-to-date version of the Guide.
</para>
<para>
This document can be found in the following places:
The newest version of this guide can always be found at <ulink
url="http://www.bugzilla.org">bugzilla.org</ulink>; including
documentation for past releases and the current development version.
</para>
<para>
<itemizedlist>
<listitem>
<para>
<ulink url="http://www.bugzilla.org/">bugzilla.org</ulink>
</para>
</listitem>
<listitem>
<para>
<ulink url="http://www.linuxdoc.org/">The Linux
Documentation Project</ulink>
</para>
</listitem>
</itemizedlist>
The documentation for the most recent stable release of Bugzilla can also
be found at
<ulink url="http://www.tldp.org">The Linux Documentation Project</ulink>.
</para>
<para>
The latest version of this document can always be checked out via CVS.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment