From sacadmin Fri Apr 25 12:29:29 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3PJTTHd003875 for ; Fri, 25 Apr 2008 12:29:29 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m3PJTP6l014864; Fri, 25 Apr 2008 20:29:27 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JZW0010HBH1YP00@nwk-avmta-1.sfbay.Sun.COM>; Fri, 25 Apr 2008 12:29:25 -0700 (PDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JZW00HOGBH10OB0@nwk-avmta-1.sfbay.Sun.COM>; Fri, 25 Apr 2008 12:29:25 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m3PJTP3k018334; Fri, 25 Apr 2008 12:29:25 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JZW00E01BDDP300@fe-sfbay-10.sun.com> (original mail from Terrence.Miller@Sun.COM); Fri, 25 Apr 2008 12:29:25 -0700 (PDT) Received: from [129.146.86.55] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JZW006EABH0CLC0@fe-sfbay-10.sun.com>; Fri, 25 Apr 2008 12:29:24 -0700 (PDT) Date: Fri, 25 Apr 2008 12:29:24 -0700 From: Terrence Miller Subject: Java DB 10.4 [LSARC/2008/277 FastTrack timeout 05/02/2008] Sender: Terrence.Miller@sun.com To: lsarc Cc: Oystein.Grovlen@sun.com, Richard.Hillgas@sun.com Message-id: <48123114.5020001@Sun.COM> Organization: Sun Microsystems MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_ttgoBpaIM+CIvqX5+WFycw)" X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.6 (X11/20070802) Status: RO Content-Length: 7963 This is a multi-part message in MIME format. --Boundary_(ID_ttgoBpaIM+CIvqX5+WFycw) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 8BIT < resent due to sac_nextcase weirdness > Template Version: @(#)onepager.txt 1.29 04/11/15 SMI This information is Copyright 2008 Sun Microsystems, Inc. 1. Introduction 1.1. Project/Component Working Name: Java DB 10.4 1.2. Name of Document Author/Supplier: Øystein Grøvlen, Oystein.Grovlen@sun.com 1.3. Date of This Document: 2008-04-10 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: DBPAC 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Heidi Bergh-Hoff, Senior Director Heidi.Bergh-Hoff@sun.com 1.4.4. The name of your business unit: Software (Database Group) 1.5. Email Aliases: 1.5.1. Responsible Manager: Geir.Hoydalsvik@sun.com 1.5.2. Responsible Engineer: Oystein.Grovlen@sun.com 1.5.3. Marketing Manager: 1.5.4. Interest List: Staale.Deraas@sun.com Lars.Heill@sun.copm 2. Project Summary 2.1. Project Description: Java DB is Sun's branding of Apache Derby, an open source pure Java database under Apache. Java DB may both run as an embedded database in the same VM as the application or as a network server. In both cases, Java DB is accessed through JDBC. This project is for a new feature release of Java DB (10.4). This release will be based on Apache Derby 10.4 and will contain several new features. 2.2. Risks and Assumptions: Java DB is based on an Apache Open Source Project officially sponsored by Sun. Several Sun developers have achieved status as comitters on this project. Sun will rely on these committers and the Sun Derby project to ensure that the project continues to meet Sun's requirements and standards. 3. Business Summary 3.1. Problem Area: The main focus of the 10.4 release is to improve Java DB's client-server story. To make this story more compelling, it has been identified five areas that needs to be worked upon: - *Performance*: Improve the Java DB performance and publish benchmarks showing Java DB to be competitive with othe OSDBs on performance. - *Scalability*: Rewrite Java DB components so that it scales well on SMP and CMT architectures (e.g. Niagara), i.e. ensure vertical scaling. - *Security*: Implement state of the art security for client-serve databases building upon the Java security model. - *High-Availability*: Create a HA story by implementing Asynchronous Replication with transparent fail-over. - *Administration*: Improve the client-server admin experience by providing JMX services fo administration. Work will also be done to provide features motivated by growing the community and growing volume: - Missing, popular SQL features. E.g. needed by popular applications. - Strengthening our position as THE Java database. E.g. VTIs and data types. - Ease of use and development,e.g.improve the Apache Derby build system. 3.2. Market/Requester: Java DB may be downloaded for free from sun.com, and it is possible for customers to buy support for Java DB from Sun. Java DB 10.4 may be bundled with future versions of Sun's JDK for Java SE 6 and Java ES. Java DB is also used in Sun xVM Ops Center. Java DB is used by several Java ES components including Application Server, Portal Server, and Service Registry. It is also supported by Netbeans. These products may choose to bundle Java DB 10.4 when it comes available. 3.3. Business Justification: Many new features will be added to Derby in the 10.4 release and these features should be made available in Java DB. 3.4. Competitive Analysis: N/A 3.5. Opportunity Window/Exposure: Target date for Java DB 10.4 is May 2008. 3.6. How will you know when you are done?: The metric of completion will be that Java DB packages of Apache Derby 10.4 will be ready to be put on developers.sun.com for download by customers. 4. Technical Description: 4.1. Details: Java DB 10.4 will be made by packaging the Apache Derby 10.4 release. 4.2. Bug/RFE Number(s) None 4.3. In Scope: N/A 4.4. Out of Scope: N/A 4.5. Interfaces: Adds support for more JDBC methods (Standard interface). Adds new SQL functionality in accordance to the SQL standard. Changes to the admin scripts/API to improve security. Changes to file format for import/export to support Blob/Clob. 4.6. Doc Impact: Documentation changes are made by the Apache Derby community. This project will rebrand the Apache Derby documentation for Java DB. 4.7. Admin/Config Impact: None 4.8. HA Impact: None 4.9. I18N/L10N Impact: All messages in Apache Derby are internationalized. Java DB depends on the Apache Derby community to provide localization. Localization of messages that are new/changed in 10.4, will not be provided for the GA release, but be added in a later update release. 4.10. Packaging & Delivery: Java DB will package and deliver the Apache Derby release as defined in LSARC 2006/345. 4.11. Security Impact: Apache Derby 10.4 adds the concept of System Priviliges. This lets the system administrator control who has permission to shut down Java DB servers and create Java DB databases. 4.12. Dependencies: Depends on Apache Derby 10.4 5. Reference Documents: (in case directory) 6. Resources and Schedule: 6.1. Projected Availability: May, 2008 6.2. Cost of Effort: QA: 8 man months Packaging: 3 man months In addition, Sun has 15 developers (incl. QE) contributing to the Apache Derby project. 6.3. Cost of Capital Resources: None 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: Java DB 6.4.3. Type of CPT Review and Approval expected: FastTrack 6.4.4. Project Boundary Conditions: 6.4.5. Is this a necessary project for OEM agreements: No 6.4.6. Notes: 6.4.7. Target RTI Date/Release: May 2008 6.4.8. Target Code Design Review Date: 6.4.9. Update approval addition: N/A 6.5. ARC review type: FastTrack 7. Prototype Availability: 7.1. Prototype Availability: N/A 7.2. Prototype Cost: N/A --Boundary_(ID_ttgoBpaIM+CIvqX5+WFycw) Content-type: text/x-vcard; name=Terrence.Miller.vcf; charset=utf-8 Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=Terrence.Miller.vcf begin:vcard fn:Terrence Miller n:Miller;Terrence adr:16 Network Circle;;UMPK-303;Menlo Park,;CA;94025;USA email;internet:terrence.miller@sun.com tel;work:650-786-9192 x-mozilla-html:FALSE version:2.1 end:vcard --Boundary_(ID_ttgoBpaIM+CIvqX5+WFycw)-- From sacadmin Fri Apr 25 13:00:13 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3PK0DxN004385 for ; Fri, 25 Apr 2008 13:00:13 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3PK0BU0013986 for <@sunmail2sca.sfbay.sun.com:lsarc@sun.com>; Fri, 25 Apr 2008 13:00:12 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JZW0062BCWBQG00@nwk-avmta-2.sfbay.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Fri, 25 Apr 2008 13:00:11 -0700 (PDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JZW001B1CWATA40@nwk-avmta-2.sfbay.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Fri, 25 Apr 2008 13:00:10 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m3PK0AGf007837 for ; Fri, 25 Apr 2008 13:00:10 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JZW00H01CLTZ300@fe-sfbay-09.sun.com> (original mail from Terrence.Miller@Sun.COM) for lsarc@sun.com (ORCPT lsarc@sun.com); Fri, 25 Apr 2008 13:00:10 -0700 (PDT) Received: from [129.146.86.55] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JZW00CESCW6DD40@fe-sfbay-09.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Fri, 25 Apr 2008 13:00:07 -0700 (PDT) Date: Fri, 25 Apr 2008 13:00:06 -0700 From: Terrence Miller Subject: (Corrected) Java DB 10.4 [LSARC/2008/277 FastTrack timeout 05/02/2008] Sender: Terrence.Miller@sun.com To: lsarc Cc: Oystein.Grovlen@sun.com, Richard.Hillegas@sun.com Message-id: <48123846.2070509@Sun.COM> Organization: Sun Microsystems MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_ZMtrGqg47dwVBxAxqi6eTQ)" X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.6 (X11/20070802) Status: RO Content-Length: 7828 This is a multi-part message in MIME format. --Boundary_(ID_ZMtrGqg47dwVBxAxqi6eTQ) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 8BIT Template Version: @(#)onepager.txt 1.29 04/11/15 SMI 1. Introduction 1.1. Project/Component Working Name: Java DB 10.4 1.2. Name of Document Author/Supplier: Øystein Grøvlen, Oystein.Grovlen@sun.com 1.3. Date of This Document: 2008-04-10 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: DBPAC 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Heidi Bergh-Hoff, Senior Director Heidi.Bergh-Hoff@sun.com 1.4.4. The name of your business unit: Software (Database Group) 1.5. Email Aliases: 1.5.1. Responsible Manager: Geir.Hoydalsvik@sun.com 1.5.2. Responsible Engineer: Oystein.Grovlen@sun.com 1.5.3. Marketing Manager: 1.5.4. Interest List: Staale.Deraas@sun.com Lars.Heill@sun.copm 2. Project Summary 2.1. Project Description: Java DB is Sun's branding of Apache Derby, an open source pure Java database under Apache. Java DB may both run as an embedded database in the same VM as the application or as a network server. In both cases, Java DB is accessed through JDBC. This project is for a new feature release of Java DB (10.4). This release will be based on Apache Derby 10.4 and will contain several new features. 2.2. Risks and Assumptions: Java DB is based on an Apache Open Source Project officially sponsored by Sun. Several Sun developers have achieved status as comitters on this project. Sun will rely on these committers and the Sun Derby project to ensure that the project continues to meet Sun's requirements and standards. 3. Business Summary 3.1. Problem Area: The main focus of the 10.4 release is to improve Java DB's client-server story. To make this story more compelling, it has been identified five areas that needs to be worked upon: - *Performance*: Improve the Java DB performance and publish benchmarks showing Java DB to be competitive with othe OSDBs on performance. - *Scalability*: Rewrite Java DB components so that it scales well on SMP and CMT architectures (e.g. Niagara), i.e. ensure vertical scaling. - *Security*: Implement state of the art security for client-serve databases building upon the Java security model. - *High-Availability*: Create a HA story by implementing Asynchronous Replication with transparent fail-over. - *Administration*: Improve the client-server admin experience by providing JMX services fo administration. Work will also be done to provide features motivated by growing the community and growing volume: - Missing, popular SQL features. E.g. needed by popular applications. - Strengthening our position as THE Java database. E.g. VTIs and data types. - Ease of use and development,e.g.improve the Apache Derby build system. 3.2. Market/Requester: Java DB may be downloaded for free from sun.com, and it is possible for customers to buy support for Java DB from Sun. Java DB 10.4 may be bundled with future versions of Sun's JDK for Java SE 6 and Java ES. Java DB is also used in Sun xVM Ops Center. Java DB is used by several Java ES components including Application Server, Portal Server, and Service Registry. It is also supported by Netbeans. These products may choose to bundle Java DB 10.4 when it comes available. 3.3. Business Justification: Many new features will be added to Derby in the 10.4 release and these features should be made available in Java DB. 3.4. Competitive Analysis: N/A 3.5. Opportunity Window/Exposure: Target date for Java DB 10.4 is May 2008. 3.6. How will you know when you are done?: The metric of completion will be that Java DB packages of Apache Derby 10.4 will be ready to be put on developers.sun.com for download by customers. 4. Technical Description: 4.1. Details: Java DB 10.4 will be made by packaging the Apache Derby 10.4 release. 4.2. Bug/RFE Number(s) None 4.3. In Scope: N/A 4.4. Out of Scope: N/A 4.5. Interfaces: Adds support for more JDBC methods (Standard interface). Adds new SQL functionality in accordance to the SQL standard. Changes to the admin scripts/API to improve security. Changes to file format for import/export to support Blob/Clob. 4.6. Doc Impact: Documentation changes are made by the Apache Derby community. This project will rebrand the Apache Derby documentation for Java DB. 4.7. Admin/Config Impact: None 4.8. HA Impact: None 4.9. I18N/L10N Impact: All messages in Apache Derby are internationalized. Java DB depends on the Apache Derby community to provide localization. Localization of messages that are new/changed in 10.4, will not be provided for the GA release, but be added in a later update release. 4.10. Packaging & Delivery: Java DB will package and deliver the Apache Derby release as defined in LSARC 2006/345. 4.11. Security Impact: Apache Derby 10.4 adds the concept of System Priviliges. This lets the system administrator control who has permission to shut down Java DB servers and create Java DB databases. 4.12. Dependencies: Depends on Apache Derby 10.4 5. Reference Documents: (in case directory) 6. Resources and Schedule: 6.1. Projected Availability: May, 2008 6.2. Cost of Effort: QA: 8 man months Packaging: 3 man months In addition, Sun has 15 developers (incl. QE) contributing to the Apache Derby project. 6.3. Cost of Capital Resources: None 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: Java DB 6.4.3. Type of CPT Review and Approval expected: FastTrack 6.4.4. Project Boundary Conditions: 6.4.5. Is this a necessary project for OEM agreements: No 6.4.6. Notes: 6.4.7. Target RTI Date/Release: May 2008 6.4.8. Target Code Design Review Date: 6.4.9. Update approval addition: N/A 6.5. ARC review type: FastTrack 7. Prototype Availability: 7.1. Prototype Availability: N/A 7.2. Prototype Cost: N/A --Boundary_(ID_ZMtrGqg47dwVBxAxqi6eTQ) Content-type: text/x-vcard; name=Terrence.Miller.vcf; charset=utf-8 Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=Terrence.Miller.vcf begin:vcard fn:Terrence Miller n:Miller;Terrence adr:16 Network Circle;;UMPK-303;Menlo Park,;CA;94025;USA email;internet:terrence.miller@sun.com tel;work:650-786-9192 x-mozilla-html:FALSE version:2.1 end:vcard --Boundary_(ID_ZMtrGqg47dwVBxAxqi6eTQ)-- From sacadmin Mon Apr 28 22:17:21 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3T5HL3o022641 for ; Mon, 28 Apr 2008 22:17:21 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3T5HKqL011592 for <@sunmail2sca.sfbay.sun.com:lsarc@sun.com>; Mon, 28 Apr 2008 22:17:21 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K0200J07MOWQB00@brm-avmta-1.central.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Mon, 28 Apr 2008 23:17:20 -0600 (MDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K0200COSMOS1RE0@brm-avmta-1.central.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Mon, 28 Apr 2008 23:17:16 -0600 (MDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m3T5HF4w007782 for ; Mon, 28 Apr 2008 22:17:15 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K0200201MK90G00@fe-sfbay-10.sun.com> (original mail from tom.childers@sun.com) for lsarc@sun.com (ORCPT lsarc@sun.com); Mon, 28 Apr 2008 22:17:15 -0700 (PDT) Received: from [192.168.15.5] ([76.191.223.250]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K02001ZAMOKM790@fe-sfbay-10.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Mon, 28 Apr 2008 22:17:15 -0700 (PDT) Date: Mon, 28 Apr 2008 22:17:00 -0700 From: Tom Childers Subject: Re: (Corrected) Java DB 10.4 [LSARC/2008/277 FastTrack timeout 05/02/2008] In-reply-to: <48123846.2070509@Sun.COM> Sender: Thomas.Childers@sun.com To: Oystein.Grovlen@sun.com Cc: lsarc , Richard.Hillegas@sun.com Message-id: MIME-version: 1.0 X-Mailer: Apple Mail (2.753) Content-type: text/plain; format=flowed; delsp=yes; charset=ISO-8859-1 X-PMX-Version: 5.4.1.325704 References: <48123846.2070509@Sun.COM> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by sac.sfbay.sun.com id m3T5HL3p022642 Status: RO Content-Length: 7653 Øystein, Is there a prior release of JavaDB that is being deprecated or dropped with this release? -tdc On Apr 25, 2008, at 1:00 PM, Terrence Miller wrote: > Template Version: @(#)onepager.txt 1.29 04/11/15 SMI > > > > 1. Introduction > 1.1. Project/Component Working Name: > > Java DB 10.4 > > 1.2. Name of Document Author/Supplier: > > Øystein Grøvlen, Oystein.Grovlen@sun.com > > 1.3. Date of This Document: > > 2008-04-10 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > 1.4.1. The PAC or CPT you expect to review your project: > > DBPAC > > 1.4.2. The ARC(s) you expect to review your project: > > LSARC > > 1.4.3. The Director/VP who is "Sponsoring" this project: > > Heidi Bergh-Hoff, Senior Director > Heidi.Bergh-Hoff@sun.com > > 1.4.4. The name of your business unit: > > Software (Database Group) > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: Geir.Hoydalsvik@sun.com > 1.5.2. Responsible Engineer: Oystein.Grovlen@sun.com > 1.5.3. Marketing Manager: > 1.5.4. Interest List: Staale.Deraas@sun.com > Lars.Heill@sun.copm > > 2. Project Summary > 2.1. Project Description: > > Java DB is Sun's branding of Apache Derby, an open source pure > Java database under Apache. Java DB may both run as an > embedded database in the same VM as the application or as a > network server. In both cases, Java DB is accessed through > JDBC. > > This project is for a new feature release of Java DB (10.4). > This release will be based on Apache Derby 10.4 and will > contain several new features. > > 2.2. Risks and Assumptions: > > Java DB is based on an Apache Open Source Project officially > sponsored by Sun. Several Sun developers have achieved status > as comitters on this project. Sun will rely on these > committers and the Sun Derby project to ensure that the > project continues to meet Sun's requirements and standards. > > 3. Business Summary > 3.1. Problem Area: > > The main focus of the 10.4 release is to improve Java DB's > client-server story. To make this story more compelling, it > has been identified five areas that needs to be worked upon: > > - *Performance*: Improve the Java DB performance and publish > benchmarks showing Java DB to be competitive with othe OSDBs > on performance. > - *Scalability*: Rewrite Java DB components so that it scales > well on SMP and CMT architectures (e.g. Niagara), > i.e. ensure vertical scaling. > - *Security*: Implement state of the art security for > client-serve databases building upon the Java security > model. > - *High-Availability*: Create a HA story by implementing > Asynchronous Replication with transparent fail-over. > - *Administration*: Improve the client-server admin experience > by providing JMX services fo administration. > > Work will also be done to provide features motivated by > growing the community and growing volume: > > - Missing, popular SQL features. E.g. needed by popular > applications. > - Strengthening our position as THE Java database. E.g. VTIs > and data types. > - Ease of use and development,e.g.improve the Apache Derby > build system. > > > 3.2. Market/Requester: > > Java DB may be downloaded for free from sun.com, and it is > possible for customers to buy support for Java DB from Sun. > > Java DB 10.4 may be bundled with future versions of Sun's JDK > for Java SE 6 and Java ES. Java DB is also used in Sun xVM > Ops Center. > > Java DB is used by several Java ES components including > Application Server, Portal Server, and Service Registry. It is > also supported by Netbeans. These products may choose to > bundle Java DB 10.4 when it comes available. > > 3.3. Business Justification: > > Many new features will be added to Derby in the 10.4 > release and > these features should be made available in Java DB. > > > 3.4. Competitive Analysis: > > N/A > > 3.5. Opportunity Window/Exposure: > > Target date for Java DB 10.4 is May 2008. > > 3.6. How will you know when you are done?: > > The metric of completion will be that Java DB packages of > Apache Derby 10.4 will be ready to be put on > developers.sun.com for download by customers. > > 4. Technical Description: > 4.1. Details: > > Java DB 10.4 will be made by packaging the Apache Derby 10.4 > release. > > 4.2. Bug/RFE Number(s) > > None > > 4.3. In Scope: > > N/A > > 4.4. Out of Scope: > > N/A > > 4.5. Interfaces: > > Adds support for more JDBC methods (Standard interface). > Adds new SQL functionality in accordance to the SQL standard. > Changes to the admin scripts/API to improve security. > Changes to file format for import/export to support Blob/Clob. > > 4.6. Doc Impact: > > Documentation changes are made by the Apache Derby community. > This project will rebrand the Apache Derby documentation for > Java DB. > > 4.7. Admin/Config Impact: > > None > > 4.8. HA Impact: > > None > > 4.9. I18N/L10N Impact: > > All messages in Apache Derby are internationalized. Java DB > depends on the Apache Derby community to provide localization. > Localization of messages that are new/changed in 10.4, will > not be provided for the GA release, but be added in a later > update release. > > 4.10. Packaging & Delivery: > > Java DB will package and deliver the Apache Derby release as > defined in LSARC 2006/345. > > 4.11. Security Impact: > > Apache Derby 10.4 adds the concept of System Priviliges. This > lets the system administrator control who has permission to > shut down Java DB servers and create Java DB > databases. > > > 4.12. Dependencies: > > Depends on Apache Derby 10.4 > > > 5. Reference Documents: > > (in case directory) > > > 6. Resources and Schedule: > 6.1. Projected Availability: > > May, 2008 > > > 6.2. Cost of Effort: > > QA: 8 man months > Packaging: 3 man months > > In addition, Sun has 15 developers (incl. QE) contributing to > the Apache Derby project. > > > 6.3. Cost of Capital Resources: > > None > > > 6.4. Product Approval Committee requested information: > 6.4.1. Consolidation or Component Name: > > Java DB > > > 6.4.3. Type of CPT Review and Approval expected: > > FastTrack > > 6.4.4. Project Boundary Conditions: > > 6.4.5. Is this a necessary project for OEM agreements: > > No > > 6.4.6. Notes: > > 6.4.7. Target RTI Date/Release: > > May 2008 > > 6.4.8. Target Code Design Review Date: > 6.4.9. Update approval addition: > > N/A > > 6.5. ARC review type: > > FastTrack > > 7. Prototype Availability: > 7.1. Prototype Availability: > > N/A > > 7.2. Prototype Cost: > > N/A > > From sacadmin Tue Apr 29 08:32:26 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3TFWQ70008096 for ; Tue, 29 Apr 2008 08:32:26 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m3TFWJa2045317 for <@sunmail2sca.sfbay.sun.com:lsarc@sun.com>; Tue, 29 Apr 2008 09:32:25 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K0300707F5Z6S00@nwk-avmta-2.sfbay.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Tue, 29 Apr 2008 08:32:23 -0700 (PDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K03006BWF5Y8Y30@nwk-avmta-2.sfbay.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Tue, 29 Apr 2008 08:32:22 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m3TFWM9s012844 for ; Tue, 29 Apr 2008 08:32:22 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K0300501F1CEG00@fe-sfbay-09.sun.com> (original mail from Richard.Hillegas@Sun.COM) for lsarc@sun.com (ORCPT lsarc@sun.com); Tue, 29 Apr 2008 08:32:22 -0700 (PDT) Received: from richard-hillegas-computer.local ([129.150.17.181]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K0300HE9F5VCRD0@fe-sfbay-09.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Tue, 29 Apr 2008 08:32:19 -0700 (PDT) Date: Tue, 29 Apr 2008 08:32:18 -0700 From: Rick Hillegas Subject: Re: (Corrected) Java DB 10.4 [LSARC/2008/277 FastTrack timeout 05/02/2008] In-reply-to: Sender: Richard.Hillegas@sun.com To: Tom Childers Cc: Oystein.Grovlen@sun.com, lsarc , Richard.Hillegas@sun.com Message-id: <48173F82.6020501@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <48123846.2070509@Sun.COM> User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) Status: RO Content-Length: 8503 Hi Tom, According to the Java DB EOL policy, this feature release deprecates releases in the 10.2 series: 10.2.1 and 10.2.2. Those releases should still be available for download for 6 months after the GA of 10.4. After that, those older releases should no longer be downloadable. Those older releases should continue to receive limited support up until 5 years after they originally went GA. The EOL policy is described here: https://clustra.norway.sun.com/twiki/bin/view/Derby/EOSL Let me know if I can provide any more information. Regards, -Rick Tom Childers wrote: > Øystein, > > Is there a prior release of JavaDB that is being deprecated or dropped > with this release? > -tdc > > > On Apr 25, 2008, at 1:00 PM, Terrence Miller wrote: > >> Template Version: @(#)onepager.txt 1.29 04/11/15 SMI >> >> >> >> 1. Introduction >> 1.1. Project/Component Working Name: >> >> Java DB 10.4 >> >> 1.2. Name of Document Author/Supplier: >> >> Øystein Grøvlen, Oystein.Grovlen@sun.com >> >> 1.3. Date of This Document: >> >> 2008-04-10 >> >> 1.4. Name of Major Document Customer(s)/Consumer(s): >> 1.4.1. The PAC or CPT you expect to review your project: >> >> DBPAC >> >> 1.4.2. The ARC(s) you expect to review your project: >> >> LSARC >> >> 1.4.3. The Director/VP who is "Sponsoring" this project: >> >> Heidi Bergh-Hoff, Senior Director >> Heidi.Bergh-Hoff@sun.com >> >> 1.4.4. The name of your business unit: >> >> Software (Database Group) >> >> 1.5. Email Aliases: >> 1.5.1. Responsible Manager: Geir.Hoydalsvik@sun.com >> 1.5.2. Responsible Engineer: Oystein.Grovlen@sun.com >> 1.5.3. Marketing Manager: >> 1.5.4. Interest List: Staale.Deraas@sun.com >> Lars.Heill@sun.copm >> >> 2. Project Summary >> 2.1. Project Description: >> >> Java DB is Sun's branding of Apache Derby, an open source pure >> Java database under Apache. Java DB may both run as an >> embedded database in the same VM as the application or as a >> network server. In both cases, Java DB is accessed through >> JDBC. >> >> This project is for a new feature release of Java DB (10.4). >> This release will be based on Apache Derby 10.4 and will >> contain several new features. >> >> 2.2. Risks and Assumptions: >> >> Java DB is based on an Apache Open Source Project officially >> sponsored by Sun. Several Sun developers have achieved status >> as comitters on this project. Sun will rely on these >> committers and the Sun Derby project to ensure that the >> project continues to meet Sun's requirements and standards. >> >> 3. Business Summary >> 3.1. Problem Area: >> >> The main focus of the 10.4 release is to improve Java DB's >> client-server story. To make this story more compelling, it >> has been identified five areas that needs to be worked upon: >> >> - *Performance*: Improve the Java DB performance and publish >> benchmarks showing Java DB to be competitive with othe OSDBs >> on performance. >> - *Scalability*: Rewrite Java DB components so that it scales >> well on SMP and CMT architectures (e.g. Niagara), >> i.e. ensure vertical scaling. >> - *Security*: Implement state of the art security for >> client-serve databases building upon the Java security >> model. >> - *High-Availability*: Create a HA story by implementing >> Asynchronous Replication with transparent fail-over. >> - *Administration*: Improve the client-server admin experience >> by providing JMX services fo administration. >> >> Work will also be done to provide features motivated by >> growing the community and growing volume: >> >> - Missing, popular SQL features. E.g. needed by popular >> applications. >> - Strengthening our position as THE Java database. E.g. VTIs >> and data types. >> - Ease of use and development,e.g.improve the Apache Derby >> build system. >> >> >> 3.2. Market/Requester: >> >> Java DB may be downloaded for free from sun.com, and it is >> possible for customers to buy support for Java DB from Sun. >> >> Java DB 10.4 may be bundled with future versions of Sun's JDK >> for Java SE 6 and Java ES. Java DB is also used in Sun xVM >> Ops Center. >> >> Java DB is used by several Java ES components including >> Application Server, Portal Server, and Service Registry. It is >> also supported by Netbeans. These products may choose to >> bundle Java DB 10.4 when it comes available. >> >> 3.3. Business Justification: >> >> Many new features will be added to Derby in the 10.4 release and >> these features should be made available in Java DB. >> >> >> 3.4. Competitive Analysis: >> >> N/A >> >> 3.5. Opportunity Window/Exposure: >> >> Target date for Java DB 10.4 is May 2008. >> >> 3.6. How will you know when you are done?: >> >> The metric of completion will be that Java DB packages of >> Apache Derby 10.4 will be ready to be put on >> developers.sun.com for download by customers. >> >> 4. Technical Description: >> 4.1. Details: >> >> Java DB 10.4 will be made by packaging the Apache Derby 10.4 >> release. >> >> 4.2. Bug/RFE Number(s) >> >> None >> >> 4.3. In Scope: >> >> N/A >> >> 4.4. Out of Scope: >> >> N/A >> >> 4.5. Interfaces: >> >> Adds support for more JDBC methods (Standard interface). >> Adds new SQL functionality in accordance to the SQL standard. >> Changes to the admin scripts/API to improve security. >> Changes to file format for import/export to support Blob/Clob. >> >> 4.6. Doc Impact: >> >> Documentation changes are made by the Apache Derby community. >> This project will rebrand the Apache Derby documentation for >> Java DB. >> >> 4.7. Admin/Config Impact: >> >> None >> >> 4.8. HA Impact: >> >> None >> >> 4.9. I18N/L10N Impact: >> >> All messages in Apache Derby are internationalized. Java DB >> depends on the Apache Derby community to provide localization. >> Localization of messages that are new/changed in 10.4, will >> not be provided for the GA release, but be added in a later >> update release. >> >> 4.10. Packaging & Delivery: >> >> Java DB will package and deliver the Apache Derby release as >> defined in LSARC 2006/345. >> >> 4.11. Security Impact: >> >> Apache Derby 10.4 adds the concept of System Priviliges. This >> lets the system administrator control who has permission to >> shut down Java DB servers and create Java DB >> databases. >> >> >> 4.12. Dependencies: >> >> Depends on Apache Derby 10.4 >> >> >> 5. Reference Documents: >> >> (in case directory) >> >> >> 6. Resources and Schedule: >> 6.1. Projected Availability: >> >> May, 2008 >> >> >> 6.2. Cost of Effort: >> >> QA: 8 man months >> Packaging: 3 man months >> >> In addition, Sun has 15 developers (incl. QE) contributing to >> the Apache Derby project. >> >> >> 6.3. Cost of Capital Resources: >> >> None >> >> >> 6.4. Product Approval Committee requested information: >> 6.4.1. Consolidation or Component Name: >> >> Java DB >> >> >> 6.4.3. Type of CPT Review and Approval expected: >> >> FastTrack >> >> 6.4.4. Project Boundary Conditions: >> >> 6.4.5. Is this a necessary project for OEM agreements: >> >> No >> >> 6.4.6. Notes: >> >> 6.4.7. Target RTI Date/Release: >> >> May 2008 >> >> 6.4.8. Target Code Design Review Date: >> 6.4.9. Update approval addition: >> >> N/A >> >> 6.5. ARC review type: >> >> FastTrack >> >> 7. Prototype Availability: >> 7.1. Prototype Availability: >> >> N/A >> >> 7.2. Prototype Cost: >> >> N/A >> >> > From sacadmin Tue Apr 29 12:20:01 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3TJJj1K017389 for ; Tue, 29 Apr 2008 12:20:01 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m3TJJfZH006393 for <@sunmail2sca.sfbay.sun.com:lsarc@sun.com>; Wed, 30 Apr 2008 03:19:45 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K0300705POUO700@brm-avmta-1.central.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Tue, 29 Apr 2008 13:19:42 -0600 (MDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K0300IURPOTVRB0@brm-avmta-1.central.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Tue, 29 Apr 2008 13:19:42 -0600 (MDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m3TJJfCV014343 for ; Tue, 29 Apr 2008 12:19:41 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K0300I01M4YPS00@fe-sfbay-09.sun.com> (original mail from tom.childers@sun.com) for lsarc@sun.com (ORCPT lsarc@sun.com); Tue, 29 Apr 2008 12:19:41 -0700 (PDT) Received: from [192.168.15.5] ([76.191.223.250]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K0300KFQPODDPB0@fe-sfbay-09.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Tue, 29 Apr 2008 12:19:30 -0700 (PDT) Date: Tue, 29 Apr 2008 12:19:08 -0700 From: Tom Childers Subject: Re: (Corrected) Java DB 10.4 [LSARC/2008/277 FastTrack timeout 05/02/2008] In-reply-to: <48173F82.6020501@sun.com> Sender: Thomas.Childers@sun.com To: Rick Hillegas Cc: Oystein.Grovlen@sun.com, lsarc Message-id: <0AAD2EF9-1E9F-4F9C-8D88-E44F5A13DEE2@sun.com> MIME-version: 1.0 X-Mailer: Apple Mail (2.753) Content-type: text/plain; format=flowed; delsp=yes; charset=ISO-8859-1 X-PMX-Version: 5.4.1.325704 References: <48123846.2070509@Sun.COM> <48173F82.6020501@sun.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by sac.sfbay.sun.com id m3TJK21L017411 Status: RO Content-Length: 9033 Perfect. Thanks for the info, Rick. I have no other issues with this fast-track. -tdc On Apr 29, 2008, at 8:32 AM, Rick Hillegas wrote: > Hi Tom, > > According to the Java DB EOL policy, this feature release > deprecates releases in the 10.2 series: 10.2.1 and 10.2.2. Those > releases should still be available for download for 6 months after > the GA of 10.4. After that, those older releases should no longer > be downloadable. Those older releases should continue to receive > limited support up until 5 years after they originally went GA. The > EOL policy is described here: https://clustra.norway.sun.com/twiki/ > bin/view/Derby/EOSL > > Let me know if I can provide any more information. > > Regards, > -Rick > > Tom Childers wrote: >> Øystein, >> >> Is there a prior release of JavaDB that is being deprecated or >> dropped with this release? >> -tdc >> >> >> On Apr 25, 2008, at 1:00 PM, Terrence Miller wrote: >> >>> Template Version: @(#)onepager.txt 1.29 04/11/15 SMI >>> >>> >>> >>> 1. Introduction >>> 1.1. Project/Component Working Name: >>> >>> Java DB 10.4 >>> >>> 1.2. Name of Document Author/Supplier: >>> >>> Øystein Grøvlen, Oystein.Grovlen@sun.com >>> >>> 1.3. Date of This Document: >>> >>> 2008-04-10 >>> >>> 1.4. Name of Major Document Customer(s)/Consumer(s): >>> 1.4.1. The PAC or CPT you expect to review your project: >>> >>> DBPAC >>> >>> 1.4.2. The ARC(s) you expect to review your project: >>> >>> LSARC >>> >>> 1.4.3. The Director/VP who is "Sponsoring" this project: >>> >>> Heidi Bergh-Hoff, Senior Director >>> Heidi.Bergh-Hoff@sun.com >>> >>> 1.4.4. The name of your business unit: >>> >>> Software (Database Group) >>> >>> 1.5. Email Aliases: >>> 1.5.1. Responsible Manager: Geir.Hoydalsvik@sun.com >>> 1.5.2. Responsible Engineer: Oystein.Grovlen@sun.com >>> 1.5.3. Marketing Manager: >>> 1.5.4. Interest List: Staale.Deraas@sun.com >>> Lars.Heill@sun.copm >>> >>> 2. Project Summary >>> 2.1. Project Description: >>> >>> Java DB is Sun's branding of Apache Derby, an open source >>> pure >>> Java database under Apache. Java DB may both run as an >>> embedded database in the same VM as the application or as a >>> network server. In both cases, Java DB is accessed through >>> JDBC. >>> >>> This project is for a new feature release of Java DB (10.4). >>> This release will be based on Apache Derby 10.4 and will >>> contain several new features. >>> >>> 2.2. Risks and Assumptions: >>> >>> Java DB is based on an Apache Open Source Project officially >>> sponsored by Sun. Several Sun developers have achieved >>> status >>> as comitters on this project. Sun will rely on these >>> committers and the Sun Derby project to ensure that the >>> project continues to meet Sun's requirements and standards. >>> >>> 3. Business Summary >>> 3.1. Problem Area: >>> >>> The main focus of the 10.4 release is to improve Java DB's >>> client-server story. To make this story more compelling, it >>> has been identified five areas that needs to be worked upon: >>> >>> - *Performance*: Improve the Java DB performance and publish >>> benchmarks showing Java DB to be competitive with othe >>> OSDBs >>> on performance. >>> - *Scalability*: Rewrite Java DB components so that it >>> scales >>> well on SMP and CMT architectures (e.g. Niagara), >>> i.e. ensure vertical scaling. >>> - *Security*: Implement state of the art security for >>> client-serve databases building upon the Java security >>> model. >>> - *High-Availability*: Create a HA story by implementing >>> Asynchronous Replication with transparent fail-over. >>> - *Administration*: Improve the client-server admin >>> experience >>> by providing JMX services fo administration. >>> >>> Work will also be done to provide features motivated by >>> growing the community and growing volume: >>> >>> - Missing, popular SQL features. E.g. needed by popular >>> applications. >>> - Strengthening our position as THE Java database. E.g. VTIs >>> and data types. >>> - Ease of use and development,e.g.improve the Apache Derby >>> build system. >>> >>> >>> 3.2. Market/Requester: >>> >>> Java DB may be downloaded for free from sun.com, and it is >>> possible for customers to buy support for Java DB from Sun. >>> >>> Java DB 10.4 may be bundled with future versions of Sun's >>> JDK >>> for Java SE 6 and Java ES. Java DB is also used in Sun xVM >>> Ops Center. >>> >>> Java DB is used by several Java ES components including >>> Application Server, Portal Server, and Service Registry. >>> It is >>> also supported by Netbeans. These products may choose to >>> bundle Java DB 10.4 when it comes available. >>> >>> 3.3. Business Justification: >>> >>> Many new features will be added to Derby in the 10.4 >>> release and >>> these features should be made available in Java DB. >>> >>> >>> 3.4. Competitive Analysis: >>> >>> N/A >>> >>> 3.5. Opportunity Window/Exposure: >>> >>> Target date for Java DB 10.4 is May 2008. >>> >>> 3.6. How will you know when you are done?: >>> >>> The metric of completion will be that Java DB packages of >>> Apache Derby 10.4 will be ready to be put on >>> developers.sun.com for download by customers. >>> >>> 4. Technical Description: >>> 4.1. Details: >>> >>> Java DB 10.4 will be made by packaging the Apache Derby 10.4 >>> release. >>> >>> 4.2. Bug/RFE Number(s) >>> >>> None >>> >>> 4.3. In Scope: >>> >>> N/A >>> >>> 4.4. Out of Scope: >>> >>> N/A >>> >>> 4.5. Interfaces: >>> >>> Adds support for more JDBC methods (Standard interface). >>> Adds new SQL functionality in accordance to the SQL >>> standard. >>> Changes to the admin scripts/API to improve security. >>> Changes to file format for import/export to support Blob/ >>> Clob. >>> >>> 4.6. Doc Impact: >>> >>> Documentation changes are made by the Apache Derby >>> community. >>> This project will rebrand the Apache Derby documentation for >>> Java DB. >>> >>> 4.7. Admin/Config Impact: >>> >>> None >>> >>> 4.8. HA Impact: >>> >>> None >>> >>> 4.9. I18N/L10N Impact: >>> >>> All messages in Apache Derby are internationalized. Java DB >>> depends on the Apache Derby community to provide >>> localization. >>> Localization of messages that are new/changed in 10.4, will >>> not be provided for the GA release, but be added in a later >>> update release. >>> >>> 4.10. Packaging & Delivery: >>> >>> Java DB will package and deliver the Apache Derby release as >>> defined in LSARC 2006/345. >>> >>> 4.11. Security Impact: >>> >>> Apache Derby 10.4 adds the concept of System Priviliges. >>> This >>> lets the system administrator control who has permission to >>> shut down Java DB servers and create Java DB >>> databases. >>> >>> >>> 4.12. Dependencies: >>> >>> Depends on Apache Derby 10.4 >>> >>> >>> 5. Reference Documents: >>> >>> (in case directory) >>> >>> >>> 6. Resources and Schedule: >>> 6.1. Projected Availability: >>> >>> May, 2008 >>> >>> >>> 6.2. Cost of Effort: >>> >>> QA: 8 man months >>> Packaging: 3 man months >>> >>> In addition, Sun has 15 developers (incl. QE) contributing to >>> the Apache Derby project. >>> >>> >>> 6.3. Cost of Capital Resources: >>> >>> None >>> >>> >>> 6.4. Product Approval Committee requested information: >>> 6.4.1. Consolidation or Component Name: >>> >>> Java DB >>> >>> >>> 6.4.3. Type of CPT Review and Approval expected: >>> >>> FastTrack >>> >>> 6.4.4. Project Boundary Conditions: >>> >>> 6.4.5. Is this a necessary project for OEM agreements: >>> >>> No >>> >>> 6.4.6. Notes: >>> >>> 6.4.7. Target RTI Date/Release: >>> >>> May 2008 >>> >>> 6.4.8. Target Code Design Review Date: >>> 6.4.9. Update approval addition: >>> >>> N/A >>> >>> 6.5. ARC review type: >>> >>> FastTrack >>> >>> 7. Prototype Availability: >>> 7.1. Prototype Availability: >>> >>> N/A >>> >>> 7.2. Prototype Cost: >>> >>> N/A >>> >>> >> >