Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of bpendleton.derby@gmail.com
 designates 209.85.211.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=RdDjPQKXRCC3X3+XUUpRUfkJSUWH1ys0dMU8zynU0qptsyWApXNzUcfh0drZUbvHw0
         RcjcBoqAU17ToXgefk0P8Zl+Gq6Uk2OnWrMMHDrI7AAv9tJozV3HdOBjE9hPzmROm5yr
         2xmVxokaaLnpU2/ZdD/lW/+Ai/qFJmvgvf3y4=
Message-ID: <4BC9DF6D.8090509@gmail.com>
Date: Sat, 17 Apr 2010 09:18:53 -0700
From: Bryan Pendleton <bpendleton.derby@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: Enabling XML Operations: Setting XALAN in CLASSPATH
References: <j2rda29c49d1004160645r4b7aac52xd0614bb7412e8da7@mail.gmail.com>
	 <4BC881F5.8090206@oracle.com>
	 <g2lda29c49d1004160921s4862d93aid68388cdda81f0e4@mail.gmail.com>
	 <4BC89961.6040906@oracle.com>
	 <i2ida29c49d1004162322u4a7f57d4rf2837dcd6910236b@mail.gmail.com>
	 <4BC9912F.40906@sun.com>
	 <u2yda29c49d1004170716xb1a8007br91270f20eeed875@mail.gmail.com>
	 <4BC9CB2B.104@gmail.com>
	 <r2sda29c49d1004170858hf2fe55f1lc39d7d5adbf3adc6@mail.gmail.com>
 <q2mda29c49d1004170901zca21312bw5c55d47f44369475@mail.gmail.com>
In-Reply-To: <q2mda29c49d1004170901zca21312bw5c55d47f44369475@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

> Yea, I would like to submit a document patch and I like to get your 
> ideas on following JIRA related information when creating a new bug.

Great! Filing and fixing documentation bugs for Derby is very much
like filing and fixing code bugs: we open an issue, prepare a patch,
review the patch, and then a committer will commit it once it is ready.

For "Affects version", you can list the Derby doc versions where you have
seen the unclear doc page appear. For example, 10.5, etc. The doc URLs
have the release id in the URL, so you can easily edit the URL such as
http://db.apache.org/derby/docs/10.5/getstart/rgsderbyrunjarsyntax.html
and replace '10.5' with '10.4' or '10.3' to check other versions. You can
specify 'dev' in that URL to see the current mainline docs.

You can leave the "fix version" empty. We update the 'fix version' when
we commit a patch, to indicate precisely which version will contain the
fix. Since that isn't known until the patch is committed, just leave it blank for now.

Once you have filed the JIRA entry, and want to start working on a
documentation patch, you'll want to refer to these guidelines:
http://db.apache.org/derby/manuals/dita.html

thanks,

bryan