Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 2018 invoked from network); 22 Aug 2008 20:39:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Aug 2008 20:39:07 -0000 Received: (qmail 59782 invoked by uid 500); 22 Aug 2008 20:39:05 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 59744 invoked by uid 500); 22 Aug 2008 20:39:05 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 59733 invoked by uid 99); 22 Aug 2008 20:39:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2008 13:39:05 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2008 20:38:16 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 2E488234C1C7 for ; Fri, 22 Aug 2008 13:38:46 -0700 (PDT) Message-ID: <674929803.1219437526188.JavaMail.jira@brutus> Date: Fri, 22 Aug 2008 13:38:46 -0700 (PDT) From: "Kim Haase (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2389) DOCS - Move Derby system and properties info from Tuning Guide into Reference Manual In-Reply-To: <29510837.1172775230664.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624975#action_12624975 ] Kim Haase commented on DERBY-2389: ---------------------------------- I think it's time to get to work on this job. Moving these topics to the Reference Manual would have some drawbacks: it might confuse readers who are used to going to the Tuning Guide for this information, and it would make the largest manual even bigger. It would also be somewhat tedious and error-prone to move and rename the topics and to fix all the references to them in the Tuning Guide and other manuals. I'm happy to do it, though. There are relatively few direct cross-references to the property topics in the Tuning Guide itself -- only about 8 that are not from other property topics. There may actually be more opportunities for direct cross-references in the Reference Manual. > DOCS - Move Derby system and properties info from Tuning Guide into Reference Manual > ------------------------------------------------------------------------------------ > > Key: DERBY-2389 > URL: https://issues.apache.org/jira/browse/DERBY-2389 > Project: Derby > Issue Type: Improvement > Components: Documentation > Reporter: Laura Stewart > Assignee: Kim Haase > > From Derby User list: > On 2/21/07, Anders Morken wrote: > > Shooting from the hip here, but one thing that has occured to me a few > > times as I've browsed the docs to figure something out is that I > > intuitively expect Derby system and database properties (especially the > > non-performance-related) to be documented in the reference guide, not > > the tuning guide. =) > On 2/21/07, Oystein Grovlen - Sun Norway wrote: > > I agree on this. I would have preferred that all "facts" where > > presented in the Reference Manual, and that the other manuals where more > > "pedagogical" presentations of the same material. Currently, it is not > > very intuitive to determine which manual has the information you are > > looking for. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.