Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 95600 invoked from network); 22 Jun 2006 16:57:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Jun 2006 16:57:02 -0000 Received: (qmail 62987 invoked by uid 500); 22 Jun 2006 16:56:58 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 62854 invoked by uid 500); 22 Jun 2006 16:56:57 -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 62792 invoked by uid 99); 22 Jun 2006 16:56:57 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jun 2006 09:56:57 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.18.42.249] (HELO nwkea-pix-1.sun.com) (192.18.42.249) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jun 2006 09:56:56 -0700 Received: from d1-sfbay-10.sun.com ([192.18.39.120]) by nwkea-pix-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id k5MGuaxG025720 for ; Thu, 22 Jun 2006 09:56:36 -0700 (PDT) Received: from conversion-daemon.d1-sfbay-10.sun.com by d1-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) id <0J1900C01TN42Y00@d1-sfbay-10.sun.com> (original mail from Richard.Hillegas@Sun.COM) for derby-dev@db.apache.org; Thu, 22 Jun 2006 09:56:35 -0700 (PDT) Received: from [129.150.20.46] by d1-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPSA id <0J1900G2BTQBR730@d1-sfbay-10.sun.com> for derby-dev@db.apache.org; Thu, 22 Jun 2006 09:56:35 -0700 (PDT) Date: Thu, 22 Jun 2006 09:56:36 -0700 From: Rick Hillegas Subject: Re: [jira] Updated: (DERBY-1271) Release documentation for JDBC4 release In-reply-to: <449AC899.3060401@apache.org> Sender: Richard.Hillegas@Sun.COM To: derby-dev@db.apache.org Message-id: <449ACBC4.9040804@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <26575551.1150918111726.JavaMail.jira@brutus> <4499D512.5000104@bristowhill.com> <449A93E6.2000809@sun.com> <449ABC9F.7010103@bristowhill.com> <449AC172.1060308@sun.com> <449AC899.3060401@apache.org> User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Daniel John Debrunner wrote: >Rick Hillegas wrote: > > > >>Jean T. Anderson wrote: >> >> >> >>>Rick Hillegas wrote: >>> >>> >>> >>> >>>>Thanks, Jean. The Edition line turns up in the visible text which >>>>appears in the printed document. That makes me think that it applies to >>>>something that the customer, the reader, cares about. I don't think the >>>>reader is particularly concerned about our transition to dita. If that >>>>is what Edition is supposed to capture, perhaps the Edition lines should >>>>be moved to a comments section so that they will not be >>>>visible/confusing to customers. >>>> >>>> >>>> >>>The Developers Guide has a "first edition" for both 10.0 and 10.1: >>> http://db.apache.org/derby/docs/10.0/manuals/develop/develop.html >>> http://db.apache.org/derby/docs/10.1/devguide/rdevcopyright.html >>> >>>I don't know why the Edition was bumped for the others. :-) >>> >>>If there isn't a major change to the content of the book, I don't think >>>the edition should be bumped. >>> >>>"Working With Derby" should definitely not be bumped from First to >>>Second edition since 10.2 will be its first release. >>> >>> >>> >>> >>I could just bump the edition for the Reference Guide, which will carry >>a lot of edits to reflect JDBC4. Would that be acceptable? >> >> > >What does the "edition" represent? Would this mean the first release of >the 10.2 documentation set would be partially at the "second edition", >doesn't seem to make sense to me. > >Dan. > > This is what's troubling me too. From Jean's investigations it seems that "edition" doesn't have a consistent meaning across our user guides and releases. We could just remove the "edition" lines. If we leave them in, then it would be good to agree on their meaning. Maybe one of the following: 1) The Edition number is bumped whenever we create a release branch. We don't bump Edition for point or patch releases. 2) The Edition number is bumped whenever reviewers agree that a user guide has changed significantly. 3) The Edition number is the same as the release number. All user guides in a given release have identical Edition numbers.