* 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 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.18rc3">
<!ENTITY bz-nextver "2.18">
<!ENTITY bz-date "2004-10-24">
-<!ENTITY % bz-devel "IGNORE">
<!ENTITY current-year "2004">
<!ENTITY landfillbase "http://landfill.bugzilla.org/bugzilla-2.18-branch/">
<!-- Header -->
<bookinfo>
- <title>The Bugzilla Guide - &bz-ver;
- <![%bz-devel;[Development ]]>Release</title>
+ <title>The Bugzilla Guide - &bz-ver; Release</title>
<authorgroup>
<corpauthor>The Bugzilla Team</corpauthor>
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!ENTITY conventions SYSTEM "conventions.xml"> ] > -->
-<!-- $Id: about.xml,v 1.16.2.2 2004/12/13 03:28:47 jake%bugzilla.org Exp $ -->
+<!-- $Id: about.xml,v 1.16.2.3 2004/12/21 20:43:12 jake%bugzilla.org Exp $ -->
<chapter id="about">
<title>About This Guide</title>
<para>
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.
- ]]>
</para>
<para>
The latest version of this guide can always be found at <ulink
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"> -->
-<!-- $Id: installation.xml,v 1.72.2.13 2004/12/18 11:56:13 jake%bugzilla.org Exp $ -->
+<!-- $Id: installation.xml,v 1.72.2.14 2004/12/21 20:43:12 jake%bugzilla.org Exp $ -->
<chapter id="installing-bugzilla">
<title>Installing Bugzilla</title>
<para>If after hearing all that, you have enough pain tolerance to attempt
installing Bugzilla on Win32, here are some pointers.
- <![%bz-devel;[
- Because this is a development version of the guide, these instructions
- are subject to change without notice. In fact, the Bugzilla Team hopes
- to have Bugzilla reasonably close to "out of
- the box" compatibility with Windows by the 2.18 release.
- ]]>
</para>
<section id="win32-perl">
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"> -->
-<!-- $Id: troubleshooting.xml,v 1.2.2.1 2004/12/08 04:10:14 jake%bugzilla.org Exp $ -->
+<!-- $Id: troubleshooting.xml,v 1.2.2.2 2004/12/21 20:43:12 jake%bugzilla.org Exp $ -->
<appendix id="troubleshooting">
<title>Troubleshooting</title>
(i.e. <quote>/bugzilla/</quote>), you can safely do this without
requiring users to delete their Bugzilla-related cookies in their
browser (this is true starting with
- <!-- Need OR logic here for bz-devel logic here -->
- Bugzilla 2.18<![%bz-devel;[, Bugzilla 2.17.7,]]> and Bugzilla 2.16.5).
+ Bugzilla 2.18 and Bugzilla 2.16.5).
</para>
</section>
log in again.
</para>
- <para>If you are using 2.18
- <![%bz-devel[(or 2.17.1 in the development series)]]>, there is a
+ <para>If you are using 2.18, there is a
parameter called <quote>loginnetmask</quote>, which you can use to set
the number of bits of the user's IP address to require to be matched when
authenticating the cookies. If you set this to something less than 32,