From James.Gates@sun.com Tue Sep 30 15:16:20 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 m8UMGJZC002887 for ; Tue, 30 Sep 2008 15:16:20 -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 m8UMGFa3027557 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Wed, 1 Oct 2008 06:16:18 +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 <0K810020Q4J4LJ00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 30 Sep 2008 16:16:16 -0600 (MDT) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K8100MLK4J3GG10@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 30 Sep 2008 16:16:16 -0600 (MDT) Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m8UMGFNV010551 for ; Tue, 30 Sep 2008 22:16:15 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K81005014G5YE00@fe-emea-10.sun.com> (original mail from James.Gates@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 30 Sep 2008 23:16:15 +0100 (BST) Received: from [192.168.1.104] ([129.150.65.34]) by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K81006WI4IK6FA0@fe-emea-10.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 30 Sep 2008 23:16:14 +0100 (BST) Date: Tue, 30 Sep 2008 18:15:08 -0400 From: James Gates Subject: EOF of PostgreSQL 8.2 in Solaris [LSARC/2008/616 timeout 10/08/2008] Sender: James.Gates@sun.com To: lsarc-ext@sun.com Message-id: <48E2A4EC.6000607@sun.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_Q7r17vwgZAMl5Afts+3SoA)" X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 8768 This is a multi-part message in MIME format. --Boundary_(ID_Q7r17vwgZAMl5Afts+3SoA) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT I'm sponsoring this on behalf of the PostgreSQL P-Team. Timeout is set for 8th October. Attached is a copy of the proposal, which can also be found in the case directory. -- Jim Gates Sun Microsystems Nashua, NH, USA http://sun.com/postgresql --Boundary_(ID_Q7r17vwgZAMl5Afts+3SoA) Content-type: text/plain; name=8.2eof__fast_track_proposal.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=8.2eof__fast_track_proposal.txt Template Version: @(#)onepager.txt 1.35 07/11/07 SMI Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: EOF of PostgreSQL 8.2 in Solaris 1.2. Name of Document Author/Supplier: James Gates 1.3. Date of This Document: 09/30/08 1.3.1. Date this project was conceived: 09/17/08 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Database PAC 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Chris.Armes@sun.com 1.4.4. The name of your business unit: Software/RPE 1.5. Email Aliases: 1.5.1. Responsible Manager: Thulasinathan.P@sun.com 1.5.2. Responsible Engineer: James.Gates@sun.com 1.5.3. Marketing Manager: Wei-Chen.Chiu@sun.com 1.5.4. Interest List: sun-postgres-pteam@sun.com [In the following, "8.1", "8.2", "8.3" or "8.4" without qualification refer to the corresponding PostgreSQL version.] 2. Project Summary 2.1. Project Description: Solaris currently includes versions 8.1, 8.2 & 8.3. It is expected that the community will release 8.4 in Dec 2008. We plan to integrate it into Solaris shortly after community release. This project proposes to announce the EOF for 8.2 in a patch release of Solaris (i.e. Solaris 10 Update) and removal of the feature in a minor release of Solaris (i.e. Solaris 11). The intention of the PostgreSQL EOL policy approved by the DB PAC is to provide active support for the latest 2 versions integrated with Solaris. Hence the release and integration of 8.4 triggers the EOF & EOL of 8.2. Note that the ARC case to EOF 8.1 was approved on 01/15/2008 (LSARC/2008/005). 2.2. Risks and Assumptions: If Solaris 11 is shipped without 8.2 it would force customers still running this version to upgrade PostgreSQL immediately if they upgrade their O/S. They might even decide not to upgrade because of this (although I think this is unlikely). Those customers who must continue to run 8.2 can still visit the community website and download the freely available software. There is also a risk that some other Sun products depend on 8.2; we need to ensure that these are upgraded to at least 8.3. I have verified that no other packages in the SFWNV consilidation are listed as depending on any of the PostgreSQL 8.2 packages. 3. Business Summary 3.1. Problem Area: The PostgreSQL community release a new major version approximately once every year. For various reasons, we need to encourage customers to upgrade to newer versions when they become available. 3.2. Market/Requester: PostgreSQL P-Team 3.3. Business Justification: We want to reduce the amount of resources needed to support and sustain old versions of PostgreSQL. We also want to keep in sync with the PostgreSQL communitys EOL policy i.e. we don't want to be in the position of having a PostgreSQL version in Solaris that is no longer supported and maintained by the community. 3.4. Competitive Analysis: N/A 3.5. Opportunity Window/Exposure: This needs to coincide with the integration of 8.4, so as to ensure that only the latest 2 versions of PostgreSQL are available/supported, and all previous versions are EOF/EOL. 3.6. How will you know when you are done?: The project will be complete when the announcement is made in a patch release of Solaris and when 8.2 is removed from a minor release of Solaris. 4. Technical Description: 4.1. Details: This project will create a release note in a Patch release of Solaris (i.e. Solaris 10 Update). It will also remove all 8.2 packages from a Minor release of Solaris (i.e., Solaris 11). The Solaris 10 Update Release Notes will be updated with the following text: PostgreSQL version 8.2 may no longer be supported in a future release. 4.2. Bug/RFE Number(s): N/A 4.3. In Scope: 4.4. Out of Scope: 4.5. Interfaces: Imported Interfaces: Interface Stability Citation --------- --------- ---------- N/A Exported Interfaces: Interface Classification Comments --------------------- --------------- ------------------------ SUNWpostgr-82-client Obsolete Package SUNWpostgr-82-contrib Obsolete Package SUNWpostgr-82-devel Obsolete Package SUNWpostgr-82-docs Obsolete Package SUNWpostgr-82-jdbc Obsolete Package SUNWpostgr-82-libs Obsolete Package SUNWpostgr-82-pl Obsolete Package SUNWpostgr-82-server Obsolete Package SUNWpostgr-82-server-data-root Obsolete Package SUNWpostgr-82-tcl Obsolete Package /lib/svc/method/postgresql Obselete SMF method script /usr/postgres/8.2 Obsolete Installation location /usr/postgres/8.2/bin Obsolete Executable location /usr/postgres/8.2/doc Obsolete Documentation /usr/postgres/8.2/etc Obsolete Config files /usr/postgres/8.2/include Obsolete Header files /usr/postgres/8.2/jdbc Obsolete JDBC driver /usr/postgres/8.2/lib Obsolete Shared libraries /usr/postgres/8.2/man Obsolete Manual pages /usr/postgres/8.2/share Obsolete Localized message files /usr/share/man/man5/postgres_82.5 Obselete Sun specific man page /var/postgres/8.2 Obselete Default db location /var/svc/manifest/application/database/postgresql.xml Obselete SMF manifest file Also deleted are all files under /usr/postgres/8.2/* (too numerous to list here). 4.6. Doc Impact: Comprehensive documentation was included with the product. This will be removed. The only other documentation impact will be the delivery of the release note (see section 4.1). 4.7. Admin/Config Impact: None. 4.8. HA Impact: N/A 4.9. I18N/L10N Impact: N/A 4.10. Packaging & Delivery: The packages listed in 4.5 will be deleted and will not be included with the first release of Solaris 11. However, note that they have been delivered with SXDE; I don't know if this will require us to go through the full EOF process. Users upgrading from Solaris 10 who are running a database under PostgreSQL 8.1 or 8.2 will have to use the upgrade solution we included with the 8.3 integration to upgrade to 8.3 or 8.4. 4.11. Security Impact: No impact. 4.12. Dependencies: Depends on the integration of 8.4 5. Reference Documents: All material associated with the original ARC case to integrate PostgreSQL 8.1 can be found at: http://sac.sfbay.sun.com/LSARC/2005/515/ Material associated with the ARC case to integrate PostgreSQL 8.2 can be found at: http://sac.sfbay.sun.com/LSARC/2006/655/ Material associated with the ARC case to integrate PostgreSQL 8.3 can be found at http://sac.sfbay.sun.com/LSARC/2008/004 PostgreSQL 8.3 information can be found at: http://www.postgresql.org/ 6. Resources and Schedule: 6.1. Projected Availability: Can be done immediately after 8.4 is integrated. 6.2. Cost of Effort: Minimal; just removal of a component. 6.3. Cost of Capital Resources: None. 6.4.1. Consolidation or Component Name: SFW 6.4.3. Type of CPT Review and Approval expected: FastTrack 6.4.4. Project Boundary Conditions: N/A 6.4.5. Is this a necessary project for OEM agreements: No 6.4.6. Notes: 6.4.7. Target RTI Date/Release: ASAP after the community releases 8.4. 6.4.8. Target Code Design Review Date: 6.4.9. Update approval addition: 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open 6.6.1. Rationale: N/A 7. Prototype Availability: 7.1. Prototype Availability: N/A 7.2. Prototype Cost: N/A --Boundary_(ID_Q7r17vwgZAMl5Afts+3SoA)-- From John.Fischer@sun.com Tue Sep 30 16:59:40 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 m8UNxdGf004588 for ; Tue, 30 Sep 2008 16:59:40 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m8UNxYv1002782 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Wed, 1 Oct 2008 00:59:38 +0100 (BST) 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 <0K8100A019BEHX00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 30 Sep 2008 17:59:38 -0600 (MDT) Received: from brmea-mail-3.sun.com ([192.18.98.34]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K8100MCR9BDGJ60@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 30 Sep 2008 17:59:37 -0600 (MDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m8UNxb9A017658 for ; Tue, 30 Sep 2008 23:59:37 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K8100L01978QQ00@mail-amer.sun.com> (original mail from John.Fischer@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 30 Sep 2008 17:59:37 -0600 (MDT) Received: from 129.145.154.66 ([129.145.154.66]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K8100B999BCRX40@mail-amer.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 30 Sep 2008 17:59:37 -0600 (MDT) Date: Tue, 30 Sep 2008 16:59:36 -0700 From: John Fischer Subject: Re: EOF of PostgreSQL 8.2 in Solaris [LSARC/2008/616 timeout 10/08/2008] In-reply-to: <48E2A4EC.6000607@sun.com> Sender: John.Fischer@sun.com To: James Gates Cc: lsarc-ext@sun.com Reply-to: John.Fischer@sun.com Message-id: <1222819176.50059.479.camel@sr1-umpk-16> MIME-version: 1.0 X-Mailer: Ximian Evolution 1.4.6.301 Content-type: text/plain; charset=ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48E2A4EC.6000607@sun.com> Status: RO Content-Length: 9483 James, Sounds like a well thought out plan. Does it make sense to add to the release note which version is recommended to migrate to in the future release? So perhaps the release note might say something like: PostgreSQL version 8.2 may no longer be supported in a future release of Solaris. You may want to migrate to PostgresSQL version 8.4. Also is there a command that should spit out the same message? Thanks, John On Tue, 2008-09-30 at 15:15, James Gates wrote: > I'm sponsoring this on behalf of the PostgreSQL P-Team. Timeout is set > for 8th October. Attached is a copy of the proposal, which can also be > found in the case directory. > > -- > Jim Gates Sun Microsystems > Nashua, NH, USA http://sun.com/postgresql > > ______________________________________________________________________ > Template Version: @(#)onepager.txt 1.35 07/11/07 SMI > Copyright 2007 Sun Microsystems > > 1. Introduction > 1.1. Project/Component Working Name: > EOF of PostgreSQL 8.2 in Solaris > > 1.2. Name of Document Author/Supplier: > James Gates > > 1.3. Date of This Document: > 09/30/08 > > 1.3.1. Date this project was conceived: > 09/17/08 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > 1.4.1. The PAC or CPT you expect to review your project: > > Database PAC > > 1.4.2. The ARC(s) you expect to review your project: > > LSARC > > 1.4.3. The Director/VP who is "Sponsoring" this project: > > Chris.Armes@sun.com > > 1.4.4. The name of your business unit: > > Software/RPE > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: Thulasinathan.P@sun.com > 1.5.2. Responsible Engineer: James.Gates@sun.com > 1.5.3. Marketing Manager: Wei-Chen.Chiu@sun.com > 1.5.4. Interest List: sun-postgres-pteam@sun.com > > [In the following, "8.1", "8.2", "8.3" or "8.4" without qualification > refer to the corresponding PostgreSQL version.] > > 2. Project Summary > 2.1. Project Description: > > Solaris currently includes versions 8.1, 8.2 & 8.3. It is expected > that the community will release 8.4 in Dec 2008. We plan to integrate > it into Solaris shortly after community release. > > This project proposes to announce the EOF for 8.2 in a patch > release of Solaris (i.e. Solaris 10 Update) and removal of the > feature in a minor release of Solaris (i.e. Solaris 11). > > The intention of the PostgreSQL EOL policy approved by the DB PAC > is to provide active support for the latest 2 versions integrated > with Solaris. Hence the release and integration of 8.4 triggers the > EOF & EOL of 8.2. > > Note that the ARC case to EOF 8.1 was approved on 01/15/2008 > (LSARC/2008/005). > > 2.2. Risks and Assumptions: > > If Solaris 11 is shipped without 8.2 it would force customers > still running this version to upgrade PostgreSQL immediately > if they upgrade their O/S. They might even decide not to > upgrade because of this (although I think this is unlikely). > Those customers who must continue to run 8.2 can still visit the > community website and download the freely available software. > > There is also a risk that some other Sun products depend on > 8.2; we need to ensure that these are upgraded to at least 8.3. > I have verified that no other packages in the SFWNV > consilidation are listed as depending on any of the PostgreSQL > 8.2 packages. > > 3. Business Summary > > 3.1. Problem Area: > > The PostgreSQL community release a new major version approximately > once every year. For various reasons, we need to encourage customers > to upgrade to newer versions when they become available. > > 3.2. Market/Requester: > > PostgreSQL P-Team > > 3.3. Business Justification: > > We want to reduce the amount of resources needed to support and sustain > old versions of PostgreSQL. We also want to keep in sync with the > PostgreSQL communitys EOL policy i.e. we don't want to > be in the position of having a PostgreSQL version in Solaris that is > no longer supported and maintained by the community. > > 3.4. Competitive Analysis: > > N/A > > 3.5. Opportunity Window/Exposure: > > This needs to coincide with the integration of 8.4, so as to ensure > that only the latest 2 versions of PostgreSQL are available/supported, > and all previous versions are EOF/EOL. > > 3.6. How will you know when you are done?: > > The project will be complete when the announcement is made in > a patch release of Solaris and when 8.2 is removed from a minor > release of Solaris. > > 4. Technical Description: > 4.1. Details: > > This project will create a release note in a Patch release of > Solaris (i.e. Solaris 10 Update). It will also remove all 8.2 > packages from a Minor release of Solaris (i.e., Solaris 11). > > The Solaris 10 Update Release Notes will be updated with the > following text: > > PostgreSQL version 8.2 may no longer be supported > in a future release. > > 4.2. Bug/RFE Number(s): > > N/A > > 4.3. In Scope: > > 4.4. Out of Scope: > > 4.5. Interfaces: > > Imported Interfaces: > Interface Stability Citation > --------- --------- ---------- > N/A > > Exported Interfaces: > Interface Classification Comments > --------------------- --------------- ------------------------ > SUNWpostgr-82-client Obsolete Package > SUNWpostgr-82-contrib Obsolete Package > SUNWpostgr-82-devel Obsolete Package > SUNWpostgr-82-docs Obsolete Package > SUNWpostgr-82-jdbc Obsolete Package > SUNWpostgr-82-libs Obsolete Package > SUNWpostgr-82-pl Obsolete Package > SUNWpostgr-82-server Obsolete Package > SUNWpostgr-82-server-data-root Obsolete Package > SUNWpostgr-82-tcl Obsolete Package > /lib/svc/method/postgresql Obselete SMF method script > /usr/postgres/8.2 Obsolete Installation location > /usr/postgres/8.2/bin Obsolete Executable location > /usr/postgres/8.2/doc Obsolete Documentation > /usr/postgres/8.2/etc Obsolete Config files > /usr/postgres/8.2/include Obsolete Header files > /usr/postgres/8.2/jdbc Obsolete JDBC driver > /usr/postgres/8.2/lib Obsolete Shared libraries > /usr/postgres/8.2/man Obsolete Manual pages > /usr/postgres/8.2/share Obsolete Localized message files > /usr/share/man/man5/postgres_82.5 Obselete Sun specific man page > /var/postgres/8.2 Obselete Default db location > /var/svc/manifest/application/database/postgresql.xml Obselete SMF manifest file > > Also deleted are all files under /usr/postgres/8.2/* (too numerous to > list here). > > 4.6. Doc Impact: > > Comprehensive documentation was included with the product. This will > be removed. The only other documentation impact will be the delivery > of the release note (see section 4.1). > > 4.7. Admin/Config Impact: > > None. > > 4.8. HA Impact: > > N/A > > 4.9. I18N/L10N Impact: > > N/A > > 4.10. Packaging & Delivery: > > The packages listed in 4.5 will be deleted and will not be > included with the first release of Solaris 11. However, note > that they have been delivered with SXDE; I don't know if this > will require us to go through the full EOF process. > > Users upgrading from Solaris 10 who are running a database > under PostgreSQL 8.1 or 8.2 will have to use the upgrade solution we > included with the 8.3 integration to upgrade to 8.3 or 8.4. > > 4.11. Security Impact: > > No impact. > > 4.12. Dependencies: > > Depends on the integration of 8.4 > > 5. Reference Documents: > > All material associated with the original ARC case to integrate > PostgreSQL 8.1 can be found at: > http://sac.sfbay.sun.com/LSARC/2005/515/ > > Material associated with the ARC case to integrate PostgreSQL > 8.2 can be found at: > http://sac.sfbay.sun.com/LSARC/2006/655/ > > Material associated with the ARC case to integrate PostgreSQL > 8.3 can be found at > http://sac.sfbay.sun.com/LSARC/2008/004 > > PostgreSQL 8.3 information can be found at: > http://www.postgresql.org/ > > 6. Resources and Schedule: > 6.1. Projected Availability: > > Can be done immediately after 8.4 is integrated. > > 6.2. Cost of Effort: > > Minimal; just removal of a component. > > 6.3. Cost of Capital Resources: > > None. > > 6.4.1. Consolidation or Component Name: > > SFW > > 6.4.3. Type of CPT Review and Approval expected: > > FastTrack > > 6.4.4. Project Boundary Conditions: > > N/A > > 6.4.5. Is this a necessary project for OEM agreements: > > No > > 6.4.6. Notes: > > 6.4.7. Target RTI Date/Release: > > ASAP after the community releases 8.4. > > 6.4.8. Target Code Design Review Date: > 6.4.9. Update approval addition: > > 6.5. ARC review type: > > FastTrack > > 6.6. ARC Exposure: > > open > > 6.6.1. Rationale: > > N/A > > 7. Prototype Availability: > 7.1. Prototype Availability: > > N/A > > 7.2. Prototype Cost: > > N/A From Bill.Walker@sun.com Tue Sep 30 17:38:03 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 m910c2UX006530 for ; Tue, 30 Sep 2008 17:38:02 -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 m910bxLk015296 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Wed, 1 Oct 2008 01:38:01 +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 <0K810070BB3BFC00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 30 Sep 2008 17:37:59 -0700 (PDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K81005H4B3A84B0@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 30 Sep 2008 17:37:58 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m910bw3T004866 for ; Wed, 01 Oct 2008 00:37:58 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K8100801B2E2800@mail-amer.sun.com> (original mail from Bill.Walker@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 30 Sep 2008 18:37:58 -0600 (MDT) Received: from [127.0.0.1] ([24.126.32.56]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K81007BVB39CR00@mail-amer.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 30 Sep 2008 18:37:58 -0600 (MDT) Date: Tue, 30 Sep 2008 20:38:08 -0400 From: Bill Walker Subject: Re: EOF of PostgreSQL 8.2 in Solaris [LSARC/2008/616 timeout 10/08/2008] In-reply-to: <1222819176.50059.479.camel@sr1-umpk-16> Sender: Bill.Walker@sun.com To: John.Fischer@sun.com Cc: James Gates , lsarc-ext@sun.com Message-id: <48E2C670.2020800@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48E2A4EC.6000607@sun.com> <1222819176.50059.479.camel@sr1-umpk-16> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17) Gecko/20080829 SeaMonkey/1.1.12 Status: RO Content-Length: 9887 Just curious, but isn't SunMC still using 8.1.4? Are plans in place over there to use the same version/packages? bill. John Fischer wrote: > James, > > Sounds like a well thought out plan. > > Does it make sense to add to the release note which > version is recommended to migrate to in the future release? > So perhaps the release note might say something like: > > PostgreSQL version 8.2 may no longer be supported > in a future release of Solaris. You may want to > migrate to PostgresSQL version 8.4. > > Also is there a command that should spit out the same > message? > > Thanks, > > John > > > On Tue, 2008-09-30 at 15:15, James Gates wrote: >> I'm sponsoring this on behalf of the PostgreSQL P-Team. Timeout is set >> for 8th October. Attached is a copy of the proposal, which can also be >> found in the case directory. >> >> -- >> Jim Gates Sun Microsystems >> Nashua, NH, USA http://sun.com/postgresql >> >> ______________________________________________________________________ >> Template Version: @(#)onepager.txt 1.35 07/11/07 SMI >> Copyright 2007 Sun Microsystems >> >> 1. Introduction >> 1.1. Project/Component Working Name: >> EOF of PostgreSQL 8.2 in Solaris >> >> 1.2. Name of Document Author/Supplier: >> James Gates >> >> 1.3. Date of This Document: >> 09/30/08 >> >> 1.3.1. Date this project was conceived: >> 09/17/08 >> >> 1.4. Name of Major Document Customer(s)/Consumer(s): >> 1.4.1. The PAC or CPT you expect to review your project: >> >> Database PAC >> >> 1.4.2. The ARC(s) you expect to review your project: >> >> LSARC >> >> 1.4.3. The Director/VP who is "Sponsoring" this project: >> >> Chris.Armes@sun.com >> >> 1.4.4. The name of your business unit: >> >> Software/RPE >> >> 1.5. Email Aliases: >> 1.5.1. Responsible Manager: Thulasinathan.P@sun.com >> 1.5.2. Responsible Engineer: James.Gates@sun.com >> 1.5.3. Marketing Manager: Wei-Chen.Chiu@sun.com >> 1.5.4. Interest List: sun-postgres-pteam@sun.com >> >> [In the following, "8.1", "8.2", "8.3" or "8.4" without qualification >> refer to the corresponding PostgreSQL version.] >> >> 2. Project Summary >> 2.1. Project Description: >> >> Solaris currently includes versions 8.1, 8.2 & 8.3. It is expected >> that the community will release 8.4 in Dec 2008. We plan to integrate >> it into Solaris shortly after community release. >> >> This project proposes to announce the EOF for 8.2 in a patch >> release of Solaris (i.e. Solaris 10 Update) and removal of the >> feature in a minor release of Solaris (i.e. Solaris 11). >> >> The intention of the PostgreSQL EOL policy approved by the DB PAC >> is to provide active support for the latest 2 versions integrated >> with Solaris. Hence the release and integration of 8.4 triggers the >> EOF & EOL of 8.2. >> >> Note that the ARC case to EOF 8.1 was approved on 01/15/2008 >> (LSARC/2008/005). >> >> 2.2. Risks and Assumptions: >> >> If Solaris 11 is shipped without 8.2 it would force customers >> still running this version to upgrade PostgreSQL immediately >> if they upgrade their O/S. They might even decide not to >> upgrade because of this (although I think this is unlikely). >> Those customers who must continue to run 8.2 can still visit the >> community website and download the freely available software. >> >> There is also a risk that some other Sun products depend on >> 8.2; we need to ensure that these are upgraded to at least 8.3. >> I have verified that no other packages in the SFWNV >> consilidation are listed as depending on any of the PostgreSQL >> 8.2 packages. >> >> 3. Business Summary >> >> 3.1. Problem Area: >> >> The PostgreSQL community release a new major version approximately >> once every year. For various reasons, we need to encourage customers >> to upgrade to newer versions when they become available. >> >> 3.2. Market/Requester: >> >> PostgreSQL P-Team >> >> 3.3. Business Justification: >> >> We want to reduce the amount of resources needed to support and sustain >> old versions of PostgreSQL. We also want to keep in sync with the >> PostgreSQL communitys EOL policy i.e. we don't want to >> be in the position of having a PostgreSQL version in Solaris that is >> no longer supported and maintained by the community. >> >> 3.4. Competitive Analysis: >> >> N/A >> >> 3.5. Opportunity Window/Exposure: >> >> This needs to coincide with the integration of 8.4, so as to ensure >> that only the latest 2 versions of PostgreSQL are available/supported, >> and all previous versions are EOF/EOL. >> >> 3.6. How will you know when you are done?: >> >> The project will be complete when the announcement is made in >> a patch release of Solaris and when 8.2 is removed from a minor >> release of Solaris. >> >> 4. Technical Description: >> 4.1. Details: >> >> This project will create a release note in a Patch release of >> Solaris (i.e. Solaris 10 Update). It will also remove all 8.2 >> packages from a Minor release of Solaris (i.e., Solaris 11). >> >> The Solaris 10 Update Release Notes will be updated with the >> following text: >> >> PostgreSQL version 8.2 may no longer be supported >> in a future release. >> >> 4.2. Bug/RFE Number(s): >> >> N/A >> >> 4.3. In Scope: >> >> 4.4. Out of Scope: >> >> 4.5. Interfaces: >> >> Imported Interfaces: >> Interface Stability Citation >> --------- --------- ---------- >> N/A >> >> Exported Interfaces: >> Interface Classification Comments >> --------------------- --------------- ------------------------ >> SUNWpostgr-82-client Obsolete Package >> SUNWpostgr-82-contrib Obsolete Package >> SUNWpostgr-82-devel Obsolete Package >> SUNWpostgr-82-docs Obsolete Package >> SUNWpostgr-82-jdbc Obsolete Package >> SUNWpostgr-82-libs Obsolete Package >> SUNWpostgr-82-pl Obsolete Package >> SUNWpostgr-82-server Obsolete Package >> SUNWpostgr-82-server-data-root Obsolete Package >> SUNWpostgr-82-tcl Obsolete Package >> /lib/svc/method/postgresql Obselete SMF method script >> /usr/postgres/8.2 Obsolete Installation location >> /usr/postgres/8.2/bin Obsolete Executable location >> /usr/postgres/8.2/doc Obsolete Documentation >> /usr/postgres/8.2/etc Obsolete Config files >> /usr/postgres/8.2/include Obsolete Header files >> /usr/postgres/8.2/jdbc Obsolete JDBC driver >> /usr/postgres/8.2/lib Obsolete Shared libraries >> /usr/postgres/8.2/man Obsolete Manual pages >> /usr/postgres/8.2/share Obsolete Localized message files >> /usr/share/man/man5/postgres_82.5 Obselete Sun specific man page >> /var/postgres/8.2 Obselete Default db location >> /var/svc/manifest/application/database/postgresql.xml Obselete SMF manifest file >> >> Also deleted are all files under /usr/postgres/8.2/* (too numerous to >> list here). >> >> 4.6. Doc Impact: >> >> Comprehensive documentation was included with the product. This will >> be removed. The only other documentation impact will be the delivery >> of the release note (see section 4.1). >> >> 4.7. Admin/Config Impact: >> >> None. >> >> 4.8. HA Impact: >> >> N/A >> >> 4.9. I18N/L10N Impact: >> >> N/A >> >> 4.10. Packaging & Delivery: >> >> The packages listed in 4.5 will be deleted and will not be >> included with the first release of Solaris 11. However, note >> that they have been delivered with SXDE; I don't know if this >> will require us to go through the full EOF process. >> >> Users upgrading from Solaris 10 who are running a database >> under PostgreSQL 8.1 or 8.2 will have to use the upgrade solution we >> included with the 8.3 integration to upgrade to 8.3 or 8.4. >> >> 4.11. Security Impact: >> >> No impact. >> >> 4.12. Dependencies: >> >> Depends on the integration of 8.4 >> >> 5. Reference Documents: >> >> All material associated with the original ARC case to integrate >> PostgreSQL 8.1 can be found at: >> http://sac.sfbay.sun.com/LSARC/2005/515/ >> >> Material associated with the ARC case to integrate PostgreSQL >> 8.2 can be found at: >> http://sac.sfbay.sun.com/LSARC/2006/655/ >> >> Material associated with the ARC case to integrate PostgreSQL >> 8.3 can be found at >> http://sac.sfbay.sun.com/LSARC/2008/004 >> >> PostgreSQL 8.3 information can be found at: >> http://www.postgresql.org/ >> >> 6. Resources and Schedule: >> 6.1. Projected Availability: >> >> Can be done immediately after 8.4 is integrated. >> >> 6.2. Cost of Effort: >> >> Minimal; just removal of a component. >> >> 6.3. Cost of Capital Resources: >> >> None. >> >> 6.4.1. Consolidation or Component Name: >> >> SFW >> >> 6.4.3. Type of CPT Review and Approval expected: >> >> FastTrack >> >> 6.4.4. Project Boundary Conditions: >> >> N/A >> >> 6.4.5. Is this a necessary project for OEM agreements: >> >> No >> >> 6.4.6. Notes: >> >> 6.4.7. Target RTI Date/Release: >> >> ASAP after the community releases 8.4. >> >> 6.4.8. Target Code Design Review Date: >> 6.4.9. Update approval addition: >> >> 6.5. ARC review type: >> >> FastTrack >> >> 6.6. ARC Exposure: >> >> open >> >> 6.6.1. Rationale: >> >> N/A >> >> 7. Prototype Availability: >> 7.1. Prototype Availability: >> >> N/A >> >> 7.2. Prototype Cost: >> >> N/A > From James.Gates@sun.com Thu Oct 2 07:15:20 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 m92EFKxj009458 for ; Thu, 2 Oct 2008 07:15:20 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m92EFGkB026286 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 2 Oct 2008 07:15:20 -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 <0K8400K3X7LJHL00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 08:15:19 -0600 (MDT) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K84002II7LIVAD0@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 08:15:18 -0600 (MDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m92EFHKQ019333 for ; Thu, 02 Oct 2008 14:15:17 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K84004016ZRPJ00@fe-emea-09.sun.com> (original mail from James.Gates@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 15:15:17 +0100 (BST) Received: from [192.168.1.104] ([129.150.65.148]) by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K8400FFS7KT5LF0@fe-emea-09.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 15:15:06 +0100 (BST) Date: Thu, 02 Oct 2008 10:14:10 -0400 From: James Gates Subject: Re: EOF of PostgreSQL 8.2 in Solaris [LSARC/2008/616 timeout 10/08/2008] In-reply-to: <1222819176.50059.479.camel@sr1-umpk-16> Sender: James.Gates@sun.com To: John.Fischer@sun.com Cc: lsarc-ext@sun.com Message-id: <48E4D732.2000408@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48E2A4EC.6000607@sun.com> <1222819176.50059.479.camel@sr1-umpk-16> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 10490 John Fischer wrote: > James, > > Sounds like a well thought out plan. > > Does it make sense to add to the release note which > version is recommended to migrate to in the future release? > So perhaps the release note might say something like: > > PostgreSQL version 8.2 may no longer be supported > in a future release of Solaris. You may want to > migrate to PostgresSQL version 8.4. > That makes sense. We can even include in the message a reference to our upgrade tool. > Also is there a command that should spit out the same > message? We hadn't planned to do this. All the 8.2 binaries are found in /usr/postgres/8.2/bin. I had anticipated that this would no longer exist after an upgrade, since all 8.2 packages will be removed. There are 3 popular commands in /usr/postgres/8.2/bin that a user would call to create, start or connect to a PostgreSQL database. I suppose when we remove the 8.2 packages from Nevada, we could add 3 scripts to /usr/postgres/8.2/bin in the 8.3 packages that print the above message. And when we EOF 8.3, add similar scripts to 8.4, etc. > > Thanks, > > John > > > On Tue, 2008-09-30 at 15:15, James Gates wrote: >> I'm sponsoring this on behalf of the PostgreSQL P-Team. Timeout is set >> for 8th October. Attached is a copy of the proposal, which can also be >> found in the case directory. >> >> -- >> Jim Gates Sun Microsystems >> Nashua, NH, USA http://sun.com/postgresql >> >> ______________________________________________________________________ >> Template Version: @(#)onepager.txt 1.35 07/11/07 SMI >> Copyright 2007 Sun Microsystems >> >> 1. Introduction >> 1.1. Project/Component Working Name: >> EOF of PostgreSQL 8.2 in Solaris >> >> 1.2. Name of Document Author/Supplier: >> James Gates >> >> 1.3. Date of This Document: >> 09/30/08 >> >> 1.3.1. Date this project was conceived: >> 09/17/08 >> >> 1.4. Name of Major Document Customer(s)/Consumer(s): >> 1.4.1. The PAC or CPT you expect to review your project: >> >> Database PAC >> >> 1.4.2. The ARC(s) you expect to review your project: >> >> LSARC >> >> 1.4.3. The Director/VP who is "Sponsoring" this project: >> >> Chris.Armes@sun.com >> >> 1.4.4. The name of your business unit: >> >> Software/RPE >> >> 1.5. Email Aliases: >> 1.5.1. Responsible Manager: Thulasinathan.P@sun.com >> 1.5.2. Responsible Engineer: James.Gates@sun.com >> 1.5.3. Marketing Manager: Wei-Chen.Chiu@sun.com >> 1.5.4. Interest List: sun-postgres-pteam@sun.com >> >> [In the following, "8.1", "8.2", "8.3" or "8.4" without qualification >> refer to the corresponding PostgreSQL version.] >> >> 2. Project Summary >> 2.1. Project Description: >> >> Solaris currently includes versions 8.1, 8.2 & 8.3. It is expected >> that the community will release 8.4 in Dec 2008. We plan to integrate >> it into Solaris shortly after community release. >> >> This project proposes to announce the EOF for 8.2 in a patch >> release of Solaris (i.e. Solaris 10 Update) and removal of the >> feature in a minor release of Solaris (i.e. Solaris 11). >> >> The intention of the PostgreSQL EOL policy approved by the DB PAC >> is to provide active support for the latest 2 versions integrated >> with Solaris. Hence the release and integration of 8.4 triggers the >> EOF & EOL of 8.2. >> >> Note that the ARC case to EOF 8.1 was approved on 01/15/2008 >> (LSARC/2008/005). >> >> 2.2. Risks and Assumptions: >> >> If Solaris 11 is shipped without 8.2 it would force customers >> still running this version to upgrade PostgreSQL immediately >> if they upgrade their O/S. They might even decide not to >> upgrade because of this (although I think this is unlikely). >> Those customers who must continue to run 8.2 can still visit the >> community website and download the freely available software. >> >> There is also a risk that some other Sun products depend on >> 8.2; we need to ensure that these are upgraded to at least 8.3. >> I have verified that no other packages in the SFWNV >> consilidation are listed as depending on any of the PostgreSQL >> 8.2 packages. >> >> 3. Business Summary >> >> 3.1. Problem Area: >> >> The PostgreSQL community release a new major version approximately >> once every year. For various reasons, we need to encourage customers >> to upgrade to newer versions when they become available. >> >> 3.2. Market/Requester: >> >> PostgreSQL P-Team >> >> 3.3. Business Justification: >> >> We want to reduce the amount of resources needed to support and sustain >> old versions of PostgreSQL. We also want to keep in sync with the >> PostgreSQL communitys EOL policy i.e. we don't want to >> be in the position of having a PostgreSQL version in Solaris that is >> no longer supported and maintained by the community. >> >> 3.4. Competitive Analysis: >> >> N/A >> >> 3.5. Opportunity Window/Exposure: >> >> This needs to coincide with the integration of 8.4, so as to ensure >> that only the latest 2 versions of PostgreSQL are available/supported, >> and all previous versions are EOF/EOL. >> >> 3.6. How will you know when you are done?: >> >> The project will be complete when the announcement is made in >> a patch release of Solaris and when 8.2 is removed from a minor >> release of Solaris. >> >> 4. Technical Description: >> 4.1. Details: >> >> This project will create a release note in a Patch release of >> Solaris (i.e. Solaris 10 Update). It will also remove all 8.2 >> packages from a Minor release of Solaris (i.e., Solaris 11). >> >> The Solaris 10 Update Release Notes will be updated with the >> following text: >> >> PostgreSQL version 8.2 may no longer be supported >> in a future release. >> >> 4.2. Bug/RFE Number(s): >> >> N/A >> >> 4.3. In Scope: >> >> 4.4. Out of Scope: >> >> 4.5. Interfaces: >> >> Imported Interfaces: >> Interface Stability Citation >> --------- --------- ---------- >> N/A >> >> Exported Interfaces: >> Interface Classification Comments >> --------------------- --------------- ------------------------ >> SUNWpostgr-82-client Obsolete Package >> SUNWpostgr-82-contrib Obsolete Package >> SUNWpostgr-82-devel Obsolete Package >> SUNWpostgr-82-docs Obsolete Package >> SUNWpostgr-82-jdbc Obsolete Package >> SUNWpostgr-82-libs Obsolete Package >> SUNWpostgr-82-pl Obsolete Package >> SUNWpostgr-82-server Obsolete Package >> SUNWpostgr-82-server-data-root Obsolete Package >> SUNWpostgr-82-tcl Obsolete Package >> /lib/svc/method/postgresql Obselete SMF method script >> /usr/postgres/8.2 Obsolete Installation location >> /usr/postgres/8.2/bin Obsolete Executable location >> /usr/postgres/8.2/doc Obsolete Documentation >> /usr/postgres/8.2/etc Obsolete Config files >> /usr/postgres/8.2/include Obsolete Header files >> /usr/postgres/8.2/jdbc Obsolete JDBC driver >> /usr/postgres/8.2/lib Obsolete Shared libraries >> /usr/postgres/8.2/man Obsolete Manual pages >> /usr/postgres/8.2/share Obsolete Localized message files >> /usr/share/man/man5/postgres_82.5 Obselete Sun specific man page >> /var/postgres/8.2 Obselete Default db location >> /var/svc/manifest/application/database/postgresql.xml Obselete SMF manifest file >> >> Also deleted are all files under /usr/postgres/8.2/* (too numerous to >> list here). >> >> 4.6. Doc Impact: >> >> Comprehensive documentation was included with the product. This will >> be removed. The only other documentation impact will be the delivery >> of the release note (see section 4.1). >> >> 4.7. Admin/Config Impact: >> >> None. >> >> 4.8. HA Impact: >> >> N/A >> >> 4.9. I18N/L10N Impact: >> >> N/A >> >> 4.10. Packaging & Delivery: >> >> The packages listed in 4.5 will be deleted and will not be >> included with the first release of Solaris 11. However, note >> that they have been delivered with SXDE; I don't know if this >> will require us to go through the full EOF process. >> >> Users upgrading from Solaris 10 who are running a database >> under PostgreSQL 8.1 or 8.2 will have to use the upgrade solution we >> included with the 8.3 integration to upgrade to 8.3 or 8.4. >> >> 4.11. Security Impact: >> >> No impact. >> >> 4.12. Dependencies: >> >> Depends on the integration of 8.4 >> >> 5. Reference Documents: >> >> All material associated with the original ARC case to integrate >> PostgreSQL 8.1 can be found at: >> http://sac.sfbay.sun.com/LSARC/2005/515/ >> >> Material associated with the ARC case to integrate PostgreSQL >> 8.2 can be found at: >> http://sac.sfbay.sun.com/LSARC/2006/655/ >> >> Material associated with the ARC case to integrate PostgreSQL >> 8.3 can be found at >> http://sac.sfbay.sun.com/LSARC/2008/004 >> >> PostgreSQL 8.3 information can be found at: >> http://www.postgresql.org/ >> >> 6. Resources and Schedule: >> 6.1. Projected Availability: >> >> Can be done immediately after 8.4 is integrated. >> >> 6.2. Cost of Effort: >> >> Minimal; just removal of a component. >> >> 6.3. Cost of Capital Resources: >> >> None. >> >> 6.4.1. Consolidation or Component Name: >> >> SFW >> >> 6.4.3. Type of CPT Review and Approval expected: >> >> FastTrack >> >> 6.4.4. Project Boundary Conditions: >> >> N/A >> >> 6.4.5. Is this a necessary project for OEM agreements: >> >> No >> >> 6.4.6. Notes: >> >> 6.4.7. Target RTI Date/Release: >> >> ASAP after the community releases 8.4. >> >> 6.4.8. Target Code Design Review Date: >> 6.4.9. Update approval addition: >> >> 6.5. ARC review type: >> >> FastTrack >> >> 6.6. ARC Exposure: >> >> open >> >> 6.6.1. Rationale: >> >> N/A >> >> 7. Prototype Availability: >> 7.1. Prototype Availability: >> >> N/A >> >> 7.2. Prototype Cost: >> >> N/A > -- Jim Gates Sun Microsystems Nashua, NH, USA http://sun.com/postgresql From James.Gates@sun.com Thu Oct 2 07:24:43 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 m92EOhqn009671 for ; Thu, 2 Oct 2008 07:24:43 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m92EOYmu051149 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 2 Oct 2008 08:24:42 -0600 (MDT) 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 <0K840030H8164K00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 07:24:42 -0700 (PDT) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K8400IH3815SE90@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 07:24:41 -0700 (PDT) Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m92EOeTf001019 for ; Thu, 02 Oct 2008 14:24:40 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K84008017LX9N00@fe-emea-10.sun.com> (original mail from James.Gates@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 15:24:40 +0100 (BST) Received: from [192.168.1.104] ([129.150.65.148]) by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K840021Y80O2A10@fe-emea-10.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 15:24:39 +0100 (BST) Date: Thu, 02 Oct 2008 10:23:39 -0400 From: James Gates Subject: Re: EOF of PostgreSQL 8.2 in Solaris [LSARC/2008/616 timeout 10/08/2008] In-reply-to: <48E2C670.2020800@Sun.COM> Sender: James.Gates@sun.com To: Bill Walker Cc: John.Fischer@sun.com, lsarc-ext@sun.com Message-id: <48E4D96B.1010604@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48E2A4EC.6000607@sun.com> <1222819176.50059.479.camel@sr1-umpk-16> <48E2C670.2020800@Sun.COM> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 11278 Yes, but we're working with them to help migrate. We can't remove 8.1 from Nevada until 1 year after EOF announcement, or until SunMC have migrated (whichever is sooner). Also, our EOL policy for PostgreSQL provides 5.5 years of support following EOL announcement (6 months grace, 2 years phase 1, 3 years phase 2). So SunMC can continue to use 8.1 on S10 for some time. Bill Walker wrote: > > Just curious, but isn't SunMC still using 8.1.4? Are plans in place > over there to use the same version/packages? > > bill. > > > John Fischer wrote: >> James, >> >> Sounds like a well thought out plan. >> Does it make sense to add to the release note which version is >> recommended to migrate to in the future release? So perhaps the >> release note might say something like: >> >> PostgreSQL version 8.2 may no longer be supported in a future >> release of Solaris. You may want to migrate to PostgresSQL >> version 8.4. >> >> Also is there a command that should spit out the same >> message? >> >> Thanks, >> >> John >> >> >> On Tue, 2008-09-30 at 15:15, James Gates wrote: >>> I'm sponsoring this on behalf of the PostgreSQL P-Team. Timeout is >>> set for 8th October. Attached is a copy of the proposal, which can >>> also be found in the case directory. >>> >>> -- >>> Jim Gates Sun Microsystems >>> Nashua, NH, USA http://sun.com/postgresql >>> >>> ______________________________________________________________________ >>> Template Version: @(#)onepager.txt 1.35 07/11/07 SMI >>> Copyright 2007 Sun Microsystems >>> >>> 1. Introduction >>> 1.1. Project/Component Working Name: >>> EOF of PostgreSQL 8.2 in Solaris >>> >>> 1.2. Name of Document Author/Supplier: >>> James Gates >>> >>> 1.3. Date of This Document: >>> 09/30/08 >>> >>> 1.3.1. Date this project was conceived: >>> 09/17/08 >>> >>> 1.4. Name of Major Document Customer(s)/Consumer(s): >>> 1.4.1. The PAC or CPT you expect to review your project: >>> >>> Database PAC >>> >>> 1.4.2. The ARC(s) you expect to review your project: >>> >>> LSARC >>> >>> 1.4.3. The Director/VP who is "Sponsoring" this project: >>> >>> Chris.Armes@sun.com >>> >>> 1.4.4. The name of your business unit: >>> >>> Software/RPE >>> >>> 1.5. Email Aliases: >>> 1.5.1. Responsible Manager: Thulasinathan.P@sun.com >>> 1.5.2. Responsible Engineer: James.Gates@sun.com >>> 1.5.3. Marketing Manager: Wei-Chen.Chiu@sun.com >>> 1.5.4. Interest List: sun-postgres-pteam@sun.com >>> >>> [In the following, "8.1", "8.2", "8.3" or "8.4" without qualification >>> refer to the corresponding PostgreSQL version.] >>> >>> 2. Project Summary >>> 2.1. Project Description: >>> >>> Solaris currently includes versions 8.1, 8.2 & 8.3. It is expected >>> that the community will release 8.4 in Dec 2008. We plan to >>> integrate >>> it into Solaris shortly after community release. >>> >>> This project proposes to announce the EOF for 8.2 in a patch >>> release of Solaris (i.e. Solaris 10 Update) and removal of the >>> feature in a minor release of Solaris (i.e. Solaris 11). >>> >>> The intention of the PostgreSQL EOL policy approved by the DB PAC >>> is to provide active support for the latest 2 versions integrated >>> with Solaris. Hence the release and integration of 8.4 triggers the >>> EOF & EOL of 8.2. >>> >>> Note that the ARC case to EOF 8.1 was approved on 01/15/2008 >>> (LSARC/2008/005). >>> >>> 2.2. Risks and Assumptions: >>> >>> If Solaris 11 is shipped without 8.2 it would force customers >>> still running this version to upgrade PostgreSQL immediately >>> if they upgrade their O/S. They might even decide not to >>> upgrade because of this (although I think this is unlikely). >>> Those customers who must continue to run 8.2 can still visit the >>> community website and download the freely available software. >>> >>> There is also a risk that some other Sun products depend on >>> 8.2; we need to ensure that these are upgraded to at least 8.3. >>> I have verified that no other packages in the SFWNV >>> consilidation are listed as depending on any of the PostgreSQL >>> 8.2 packages. >>> >>> 3. Business Summary >>> >>> 3.1. Problem Area: >>> >>> The PostgreSQL community release a new major version approximately >>> once every year. For various reasons, we need to encourage customers >>> to upgrade to newer versions when they become available. >>> >>> 3.2. Market/Requester: >>> >>> PostgreSQL P-Team >>> >>> 3.3. Business Justification: >>> >>> We want to reduce the amount of resources needed to support >>> and sustain >>> old versions of PostgreSQL. We also want to keep in sync with >>> the >>> PostgreSQL communitys EOL policy i.e. we don't want to >>> be in the position of having a PostgreSQL version in Solaris that is >>> no longer supported and maintained by the community. >>> >>> 3.4. Competitive Analysis: >>> >>> N/A >>> >>> 3.5. Opportunity Window/Exposure: >>> >>> This needs to coincide with the integration of 8.4, so as to >>> ensure >>> that only the latest 2 versions of PostgreSQL are >>> available/supported, >>> and all previous versions are EOF/EOL. >>> >>> 3.6. How will you know when you are done?: >>> >>> The project will be complete when the announcement is made in >>> a patch release of Solaris and when 8.2 is removed from a minor >>> release of Solaris. >>> >>> 4. Technical Description: >>> 4.1. Details: >>> >>> This project will create a release note in a Patch release of >>> Solaris (i.e. Solaris 10 Update). It will also remove all 8.2 >>> packages from a Minor release of Solaris (i.e., Solaris 11). >>> >>> The Solaris 10 Update Release Notes will be updated with the >>> following text: >>> >>> PostgreSQL version 8.2 may no longer be supported in >>> a future release. >>> 4.2. Bug/RFE Number(s): >>> >>> N/A >>> 4.3. In Scope: >>> >>> 4.4. Out of Scope: >>> 4.5. Interfaces: >>> >>> Imported Interfaces: >>> Interface Stability Citation >>> --------- --------- ---------- >>> N/A >>> >>> Exported Interfaces: >>> Interface Classification Comments >>> --------------------- --------------- >>> ------------------------ >>> SUNWpostgr-82-client Obsolete Package >>> SUNWpostgr-82-contrib Obsolete Package >>> SUNWpostgr-82-devel Obsolete Package >>> SUNWpostgr-82-docs Obsolete Package >>> SUNWpostgr-82-jdbc Obsolete Package >>> SUNWpostgr-82-libs Obsolete Package >>> SUNWpostgr-82-pl Obsolete Package >>> SUNWpostgr-82-server Obsolete Package >>> SUNWpostgr-82-server-data-root Obsolete Package >>> SUNWpostgr-82-tcl Obsolete Package >>> /lib/svc/method/postgresql Obselete SMF method script >>> /usr/postgres/8.2 Obsolete Installation location >>> /usr/postgres/8.2/bin Obsolete Executable location >>> /usr/postgres/8.2/doc Obsolete Documentation >>> /usr/postgres/8.2/etc Obsolete Config files >>> /usr/postgres/8.2/include Obsolete Header files >>> /usr/postgres/8.2/jdbc Obsolete JDBC driver >>> /usr/postgres/8.2/lib Obsolete Shared libraries >>> /usr/postgres/8.2/man Obsolete Manual pages >>> /usr/postgres/8.2/share Obsolete Localized message files >>> /usr/share/man/man5/postgres_82.5 Obselete Sun specific man >>> page >>> /var/postgres/8.2 Obselete Default db location >>> /var/svc/manifest/application/database/postgresql.xml >>> Obselete SMF manifest file >>> >>> Also deleted are all files under /usr/postgres/8.2/* (too >>> numerous to >>> list here). >>> >>> 4.6. Doc Impact: >>> >>> Comprehensive documentation was included with the product. This will >>> be removed. The only other documentation impact will be the delivery >>> of the release note (see section 4.1). >>> >>> 4.7. Admin/Config Impact: >>> >>> None. >>> 4.8. HA Impact: >>> >>> N/A >>> 4.9. I18N/L10N Impact: >>> >>> N/A >>> 4.10. Packaging & Delivery: >>> >>> The packages listed in 4.5 will be deleted and will not be >>> included with the first release of Solaris 11. However, note >>> that they have been delivered with SXDE; I don't know if this >>> will require us to go through the full EOF process. >>> >>> Users upgrading from Solaris 10 who are running a database >>> under PostgreSQL 8.1 or 8.2 will have to use the upgrade >>> solution we >>> included with the 8.3 integration to upgrade to 8.3 or 8.4. >>> >>> 4.11. Security Impact: >>> >>> No impact. >>> 4.12. Dependencies: >>> >>> Depends on the integration of 8.4 >>> >>> 5. Reference Documents: >>> >>> All material associated with the original ARC case to integrate >>> PostgreSQL 8.1 can be found at: >>> http://sac.sfbay.sun.com/LSARC/2005/515/ >>> >>> Material associated with the ARC case to integrate PostgreSQL >>> 8.2 can be found at: >>> http://sac.sfbay.sun.com/LSARC/2006/655/ >>> >>> Material associated with the ARC case to integrate PostgreSQL >>> 8.3 can be found at >>> http://sac.sfbay.sun.com/LSARC/2008/004 >>> >>> PostgreSQL 8.3 information can be found at: >>> http://www.postgresql.org/ >>> >>> 6. Resources and Schedule: >>> 6.1. Projected Availability: >>> >>> Can be done immediately after 8.4 is integrated. >>> >>> 6.2. Cost of Effort: >>> >>> Minimal; just removal of a component. >>> >>> 6.3. Cost of Capital Resources: >>> >>> None. >>> >>> 6.4.1. Consolidation or Component Name: >>> >>> SFW >>> >>> 6.4.3. Type of CPT Review and Approval expected: >>> >>> FastTrack >>> >>> 6.4.4. Project Boundary Conditions: >>> >>> N/A >>> >>> 6.4.5. Is this a necessary project for OEM agreements: >>> >>> No >>> >>> 6.4.6. Notes: >>> >>> 6.4.7. Target RTI Date/Release: >>> >>> ASAP after the community releases 8.4. >>> >>> 6.4.8. Target Code Design Review Date: >>> 6.4.9. Update approval addition: >>> >>> 6.5. ARC review type: >>> >>> FastTrack >>> >>> 6.6. ARC Exposure: >>> >>> open >>> >>> 6.6.1. Rationale: >>> >>> N/A >>> >>> 7. Prototype Availability: >>> 7.1. Prototype Availability: >>> >>> N/A >>> >>> 7.2. Prototype Cost: >>> >>> N/A >> > -- Jim Gates Sun Microsystems Nashua, NH, USA http://sun.com/postgresql From John.Fischer@Sun.com Thu Oct 2 08:30:25 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 m92FUOxc012090 for ; Thu, 2 Oct 2008 08:30:24 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m92FUM1C000103 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 2 Oct 2008 08:30:24 -0700 (PDT) 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 <0K840090HB2N4M00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 08:30:23 -0700 (PDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K8400737B2M1920@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 08:30:23 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m92FUMWS003604 for ; Thu, 02 Oct 2008 15:30:22 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K840060198BLZ00@mail-amer.sun.com> (original mail from John.Fischer@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 09:30:22 -0600 (MDT) Received: from 129.145.154.66 ([129.145.154.66]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K84007Y3B27TF30@mail-amer.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 09:30:07 -0600 (MDT) Date: Thu, 02 Oct 2008 08:30:07 -0700 From: John Fischer Subject: Re: EOF of PostgreSQL 8.2 in Solaris [LSARC/2008/616 timeout 10/08/2008] In-reply-to: <48E4D732.2000408@sun.com> Sender: John.Fischer@Sun.com To: James Gates Cc: John Fischer , lsarc-ext@Sun.com Reply-to: John.Fischer@Sun.com Message-id: <1222961406.50059.2859.camel@sr1-umpk-16> MIME-version: 1.0 X-Mailer: Ximian Evolution 1.4.6.301 Content-type: text/plain; charset=ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48E2A4EC.6000607@sun.com> <1222819176.50059.479.camel@sr1-umpk-16> <48E4D732.2000408@sun.com> Status: RO Content-Length: 12284 James, The application warning message would be from the previous release. So you would need to patch an application or applications with the message for Solaris 10. This should occur at the same time as the release notes are updated. The reason why this is desirable is because many of the those using the product might not even see the release notes or read a man page. That is why the EOF procedures document found at: http://sac.sfbay/cgi-bin/bp.cgi?NAME=Obsolete-EOF.bp suggests: Where technically feasible, inclusion in the release where the interface is declared Obsolete of a warning mechanism if the interface is used. It goes on to suggest a log warning could be used. So in the Patch release of Solaris where the release note will be updated it would be really good and if technically feasible to also have a mechanism for the EOF message to be declared automatically. When I've Obsoleted an interface I have done a popup dialog because I deal with GUIs. However, in this case a system log or to standard error would be sufficient. Thanks, John On Thu, 2008-10-02 at 07:14, James Gates wrote: > John Fischer wrote: > > James, > > > > Sounds like a well thought out plan. > > > > Does it make sense to add to the release note which > > version is recommended to migrate to in the future release? > > So perhaps the release note might say something like: > > > > PostgreSQL version 8.2 may no longer be supported > > in a future release of Solaris. You may want to > > migrate to PostgresSQL version 8.4. > > > That makes sense. We can even include in the message a reference to our > upgrade tool. > > Also is there a command that should spit out the same > > message? > We hadn't planned to do this. > > All the 8.2 binaries are found in /usr/postgres/8.2/bin. I had > anticipated that this would no longer exist after an upgrade, since all > 8.2 packages will be removed. > > There are 3 popular commands in /usr/postgres/8.2/bin that a user would > call to create, start or connect to a PostgreSQL database. > > I suppose when we remove the 8.2 packages from Nevada, we could add 3 > scripts to /usr/postgres/8.2/bin in the 8.3 packages that print the > above message. And when we EOF 8.3, add similar scripts to 8.4, etc. > > > > Thanks, > > > > John > > > > > > On Tue, 2008-09-30 at 15:15, James Gates wrote: > >> I'm sponsoring this on behalf of the PostgreSQL P-Team. Timeout is set > >> for 8th October. Attached is a copy of the proposal, which can also be > >> found in the case directory. > >> > >> -- > >> Jim Gates Sun Microsystems > >> Nashua, NH, USA http://sun.com/postgresql > >> > >> ______________________________________________________________________ > >> Template Version: @(#)onepager.txt 1.35 07/11/07 SMI > >> Copyright 2007 Sun Microsystems > >> > >> 1. Introduction > >> 1.1. Project/Component Working Name: > >> EOF of PostgreSQL 8.2 in Solaris > >> > >> 1.2. Name of Document Author/Supplier: > >> James Gates > >> > >> 1.3. Date of This Document: > >> 09/30/08 > >> > >> 1.3.1. Date this project was conceived: > >> 09/17/08 > >> > >> 1.4. Name of Major Document Customer(s)/Consumer(s): > >> 1.4.1. The PAC or CPT you expect to review your project: > >> > >> Database PAC > >> > >> 1.4.2. The ARC(s) you expect to review your project: > >> > >> LSARC > >> > >> 1.4.3. The Director/VP who is "Sponsoring" this project: > >> > >> Chris.Armes@sun.com > >> > >> 1.4.4. The name of your business unit: > >> > >> Software/RPE > >> > >> 1.5. Email Aliases: > >> 1.5.1. Responsible Manager: Thulasinathan.P@sun.com > >> 1.5.2. Responsible Engineer: James.Gates@sun.com > >> 1.5.3. Marketing Manager: Wei-Chen.Chiu@sun.com > >> 1.5.4. Interest List: sun-postgres-pteam@sun.com > >> > >> [In the following, "8.1", "8.2", "8.3" or "8.4" without qualification > >> refer to the corresponding PostgreSQL version.] > >> > >> 2. Project Summary > >> 2.1. Project Description: > >> > >> Solaris currently includes versions 8.1, 8.2 & 8.3. It is expected > >> that the community will release 8.4 in Dec 2008. We plan to integrate > >> it into Solaris shortly after community release. > >> > >> This project proposes to announce the EOF for 8.2 in a patch > >> release of Solaris (i.e. Solaris 10 Update) and removal of the > >> feature in a minor release of Solaris (i.e. Solaris 11). > >> > >> The intention of the PostgreSQL EOL policy approved by the DB PAC > >> is to provide active support for the latest 2 versions integrated > >> with Solaris. Hence the release and integration of 8.4 triggers the > >> EOF & EOL of 8.2. > >> > >> Note that the ARC case to EOF 8.1 was approved on 01/15/2008 > >> (LSARC/2008/005). > >> > >> 2.2. Risks and Assumptions: > >> > >> If Solaris 11 is shipped without 8.2 it would force customers > >> still running this version to upgrade PostgreSQL immediately > >> if they upgrade their O/S. They might even decide not to > >> upgrade because of this (although I think this is unlikely). > >> Those customers who must continue to run 8.2 can still visit the > >> community website and download the freely available software. > >> > >> There is also a risk that some other Sun products depend on > >> 8.2; we need to ensure that these are upgraded to at least 8.3. > >> I have verified that no other packages in the SFWNV > >> consilidation are listed as depending on any of the PostgreSQL > >> 8.2 packages. > >> > >> 3. Business Summary > >> > >> 3.1. Problem Area: > >> > >> The PostgreSQL community release a new major version approximately > >> once every year. For various reasons, we need to encourage customers > >> to upgrade to newer versions when they become available. > >> > >> 3.2. Market/Requester: > >> > >> PostgreSQL P-Team > >> > >> 3.3. Business Justification: > >> > >> We want to reduce the amount of resources needed to support and sustain > >> old versions of PostgreSQL. We also want to keep in sync with the > >> PostgreSQL communitys EOL policy i.e. we don't want to > >> be in the position of having a PostgreSQL version in Solaris that is > >> no longer supported and maintained by the community. > >> > >> 3.4. Competitive Analysis: > >> > >> N/A > >> > >> 3.5. Opportunity Window/Exposure: > >> > >> This needs to coincide with the integration of 8.4, so as to ensure > >> that only the latest 2 versions of PostgreSQL are available/supported, > >> and all previous versions are EOF/EOL. > >> > >> 3.6. How will you know when you are done?: > >> > >> The project will be complete when the announcement is made in > >> a patch release of Solaris and when 8.2 is removed from a minor > >> release of Solaris. > >> > >> 4. Technical Description: > >> 4.1. Details: > >> > >> This project will create a release note in a Patch release of > >> Solaris (i.e. Solaris 10 Update). It will also remove all 8.2 > >> packages from a Minor release of Solaris (i.e., Solaris 11). > >> > >> The Solaris 10 Update Release Notes will be updated with the > >> following text: > >> > >> PostgreSQL version 8.2 may no longer be supported > >> in a future release. > >> > >> 4.2. Bug/RFE Number(s): > >> > >> N/A > >> > >> 4.3. In Scope: > >> > >> 4.4. Out of Scope: > >> > >> 4.5. Interfaces: > >> > >> Imported Interfaces: > >> Interface Stability Citation > >> --------- --------- ---------- > >> N/A > >> > >> Exported Interfaces: > >> Interface Classification Comments > >> --------------------- --------------- ------------------------ > >> SUNWpostgr-82-client Obsolete Package > >> SUNWpostgr-82-contrib Obsolete Package > >> SUNWpostgr-82-devel Obsolete Package > >> SUNWpostgr-82-docs Obsolete Package > >> SUNWpostgr-82-jdbc Obsolete Package > >> SUNWpostgr-82-libs Obsolete Package > >> SUNWpostgr-82-pl Obsolete Package > >> SUNWpostgr-82-server Obsolete Package > >> SUNWpostgr-82-server-data-root Obsolete Package > >> SUNWpostgr-82-tcl Obsolete Package > >> /lib/svc/method/postgresql Obselete SMF method script > >> /usr/postgres/8.2 Obsolete Installation location > >> /usr/postgres/8.2/bin Obsolete Executable location > >> /usr/postgres/8.2/doc Obsolete Documentation > >> /usr/postgres/8.2/etc Obsolete Config files > >> /usr/postgres/8.2/include Obsolete Header files > >> /usr/postgres/8.2/jdbc Obsolete JDBC driver > >> /usr/postgres/8.2/lib Obsolete Shared libraries > >> /usr/postgres/8.2/man Obsolete Manual pages > >> /usr/postgres/8.2/share Obsolete Localized message files > >> /usr/share/man/man5/postgres_82.5 Obselete Sun specific man page > >> /var/postgres/8.2 Obselete Default db location > >> /var/svc/manifest/application/database/postgresql.xml Obselete SMF manifest file > >> > >> Also deleted are all files under /usr/postgres/8.2/* (too numerous to > >> list here). > >> > >> 4.6. Doc Impact: > >> > >> Comprehensive documentation was included with the product. This will > >> be removed. The only other documentation impact will be the delivery > >> of the release note (see section 4.1). > >> > >> 4.7. Admin/Config Impact: > >> > >> None. > >> > >> 4.8. HA Impact: > >> > >> N/A > >> > >> 4.9. I18N/L10N Impact: > >> > >> N/A > >> > >> 4.10. Packaging & Delivery: > >> > >> The packages listed in 4.5 will be deleted and will not be > >> included with the first release of Solaris 11. However, note > >> that they have been delivered with SXDE; I don't know if this > >> will require us to go through the full EOF process. > >> > >> Users upgrading from Solaris 10 who are running a database > >> under PostgreSQL 8.1 or 8.2 will have to use the upgrade solution we > >> included with the 8.3 integration to upgrade to 8.3 or 8.4. > >> > >> 4.11. Security Impact: > >> > >> No impact. > >> > >> 4.12. Dependencies: > >> > >> Depends on the integration of 8.4 > >> > >> 5. Reference Documents: > >> > >> All material associated with the original ARC case to integrate > >> PostgreSQL 8.1 can be found at: > >> http://sac.sfbay.sun.com/LSARC/2005/515/ > >> > >> Material associated with the ARC case to integrate PostgreSQL > >> 8.2 can be found at: > >> http://sac.sfbay.sun.com/LSARC/2006/655/ > >> > >> Material associated with the ARC case to integrate PostgreSQL > >> 8.3 can be found at > >> http://sac.sfbay.sun.com/LSARC/2008/004 > >> > >> PostgreSQL 8.3 information can be found at: > >> http://www.postgresql.org/ > >> > >> 6. Resources and Schedule: > >> 6.1. Projected Availability: > >> > >> Can be done immediately after 8.4 is integrated. > >> > >> 6.2. Cost of Effort: > >> > >> Minimal; just removal of a component. > >> > >> 6.3. Cost of Capital Resources: > >> > >> None. > >> > >> 6.4.1. Consolidation or Component Name: > >> > >> SFW > >> > >> 6.4.3. Type of CPT Review and Approval expected: > >> > >> FastTrack > >> > >> 6.4.4. Project Boundary Conditions: > >> > >> N/A > >> > >> 6.4.5. Is this a necessary project for OEM agreements: > >> > >> No > >> > >> 6.4.6. Notes: > >> > >> 6.4.7. Target RTI Date/Release: > >> > >> ASAP after the community releases 8.4. > >> > >> 6.4.8. Target Code Design Review Date: > >> 6.4.9. Update approval addition: > >> > >> 6.5. ARC review type: > >> > >> FastTrack > >> > >> 6.6. ARC Exposure: > >> > >> open > >> > >> 6.6.1. Rationale: > >> > >> N/A > >> > >> 7. Prototype Availability: > >> 7.1. Prototype Availability: > >> > >> N/A > >> > >> 7.2. Prototype Cost: > >> > >> N/A > > > > -- > Jim Gates Sun Microsystems > Nashua, NH, USA http://sun.com/postgresql From James.Gates@sun.com Thu Oct 2 08:59:09 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 m92Fx9G4012867 for ; Thu, 2 Oct 2008 08:59:09 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m92Fx5qH029721 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 2 Oct 2008 09:59:09 -0600 (MDT) 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 <0K8400B1ZCEINV00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 08:59:06 -0700 (PDT) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K84007IYCEG1730@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 08:59:05 -0700 (PDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m92Fx4mV013247 for ; Thu, 02 Oct 2008 15:59:04 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K8400L01C0AZR00@fe-emea-09.sun.com> (original mail from James.Gates@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 16:59:04 +0100 (BST) Received: from [192.168.1.104] ([129.150.65.148]) by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K84009Q0CE2KZ10@fe-emea-09.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 16:59:03 +0100 (BST) Date: Thu, 02 Oct 2008 11:58:06 -0400 From: James Gates Subject: Re: EOF of PostgreSQL 8.2 in Solaris [LSARC/2008/616 timeout 10/08/2008] In-reply-to: <1222961406.50059.2859.camel@sr1-umpk-16> Sender: James.Gates@sun.com To: John.Fischer@sun.com Cc: lsarc-ext@sun.com Message-id: <48E4EF8E.2040602@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48E2A4EC.6000607@sun.com> <1222819176.50059.479.camel@sr1-umpk-16> <48E4D732.2000408@sun.com> <1222961406.50059.2859.camel@sr1-umpk-16> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 12922 Oh, I see. We would have to modify the community code to include a call to syslog(3), but I don't see that as too much of a problem. I think the biggest issue is, for S10, this can only be issued in a patch. So we're relying on people who don't read release notes to keep up to date with the latest patches. Therefore there's a good chance that no one will ever see the syslog message, but since it's technically feasible to do, we will do it. John Fischer wrote: > James, > > The application warning message would be from the previous > release. So you would need to patch an application or applications > with the message for Solaris 10. This should occur at the > same time as the release notes are updated. The reason why > this is desirable is because many of the those using the > product might not even see the release notes or read a > man page. That is why the EOF procedures document found > at: > > http://sac.sfbay/cgi-bin/bp.cgi?NAME=Obsolete-EOF.bp > > suggests: > > Where technically feasible, inclusion in the release > where the interface is declared Obsolete of a warning > mechanism if the interface is used. > > It goes on to suggest a log warning could be used. > > So in the Patch release of Solaris where the release note > will be updated it would be really good and if technically > feasible to also have a mechanism for the EOF message to > be declared automatically. When I've Obsoleted an interface > I have done a popup dialog because I deal with GUIs. However, > in this case a system log or to standard error would be sufficient. > > Thanks, > > John > > On Thu, 2008-10-02 at 07:14, James Gates wrote: >> John Fischer wrote: >>> James, >>> >>> Sounds like a well thought out plan. >>> >>> Does it make sense to add to the release note which >>> version is recommended to migrate to in the future release? >>> So perhaps the release note might say something like: >>> >>> PostgreSQL version 8.2 may no longer be supported >>> in a future release of Solaris. You may want to >>> migrate to PostgresSQL version 8.4. >>> >> That makes sense. We can even include in the message a reference to our >> upgrade tool. >>> Also is there a command that should spit out the same >>> message? >> We hadn't planned to do this. >> >> All the 8.2 binaries are found in /usr/postgres/8.2/bin. I had >> anticipated that this would no longer exist after an upgrade, since all >> 8.2 packages will be removed. >> >> There are 3 popular commands in /usr/postgres/8.2/bin that a user would >> call to create, start or connect to a PostgreSQL database. >> >> I suppose when we remove the 8.2 packages from Nevada, we could add 3 >> scripts to /usr/postgres/8.2/bin in the 8.3 packages that print the >> above message. And when we EOF 8.3, add similar scripts to 8.4, etc. >>> Thanks, >>> >>> John >>> >>> >>> On Tue, 2008-09-30 at 15:15, James Gates wrote: >>>> I'm sponsoring this on behalf of the PostgreSQL P-Team. Timeout is set >>>> for 8th October. Attached is a copy of the proposal, which can also be >>>> found in the case directory. >>>> >>>> -- >>>> Jim Gates Sun Microsystems >>>> Nashua, NH, USA http://sun.com/postgresql >>>> >>>> ______________________________________________________________________ >>>> Template Version: @(#)onepager.txt 1.35 07/11/07 SMI >>>> Copyright 2007 Sun Microsystems >>>> >>>> 1. Introduction >>>> 1.1. Project/Component Working Name: >>>> EOF of PostgreSQL 8.2 in Solaris >>>> >>>> 1.2. Name of Document Author/Supplier: >>>> James Gates >>>> >>>> 1.3. Date of This Document: >>>> 09/30/08 >>>> >>>> 1.3.1. Date this project was conceived: >>>> 09/17/08 >>>> >>>> 1.4. Name of Major Document Customer(s)/Consumer(s): >>>> 1.4.1. The PAC or CPT you expect to review your project: >>>> >>>> Database PAC >>>> >>>> 1.4.2. The ARC(s) you expect to review your project: >>>> >>>> LSARC >>>> >>>> 1.4.3. The Director/VP who is "Sponsoring" this project: >>>> >>>> Chris.Armes@sun.com >>>> >>>> 1.4.4. The name of your business unit: >>>> >>>> Software/RPE >>>> >>>> 1.5. Email Aliases: >>>> 1.5.1. Responsible Manager: Thulasinathan.P@sun.com >>>> 1.5.2. Responsible Engineer: James.Gates@sun.com >>>> 1.5.3. Marketing Manager: Wei-Chen.Chiu@sun.com >>>> 1.5.4. Interest List: sun-postgres-pteam@sun.com >>>> >>>> [In the following, "8.1", "8.2", "8.3" or "8.4" without qualification >>>> refer to the corresponding PostgreSQL version.] >>>> >>>> 2. Project Summary >>>> 2.1. Project Description: >>>> >>>> Solaris currently includes versions 8.1, 8.2 & 8.3. It is expected >>>> that the community will release 8.4 in Dec 2008. We plan to integrate >>>> it into Solaris shortly after community release. >>>> >>>> This project proposes to announce the EOF for 8.2 in a patch >>>> release of Solaris (i.e. Solaris 10 Update) and removal of the >>>> feature in a minor release of Solaris (i.e. Solaris 11). >>>> >>>> The intention of the PostgreSQL EOL policy approved by the DB PAC >>>> is to provide active support for the latest 2 versions integrated >>>> with Solaris. Hence the release and integration of 8.4 triggers the >>>> EOF & EOL of 8.2. >>>> >>>> Note that the ARC case to EOF 8.1 was approved on 01/15/2008 >>>> (LSARC/2008/005). >>>> >>>> 2.2. Risks and Assumptions: >>>> >>>> If Solaris 11 is shipped without 8.2 it would force customers >>>> still running this version to upgrade PostgreSQL immediately >>>> if they upgrade their O/S. They might even decide not to >>>> upgrade because of this (although I think this is unlikely). >>>> Those customers who must continue to run 8.2 can still visit the >>>> community website and download the freely available software. >>>> >>>> There is also a risk that some other Sun products depend on >>>> 8.2; we need to ensure that these are upgraded to at least 8.3. >>>> I have verified that no other packages in the SFWNV >>>> consilidation are listed as depending on any of the PostgreSQL >>>> 8.2 packages. >>>> >>>> 3. Business Summary >>>> >>>> 3.1. Problem Area: >>>> >>>> The PostgreSQL community release a new major version approximately >>>> once every year. For various reasons, we need to encourage customers >>>> to upgrade to newer versions when they become available. >>>> >>>> 3.2. Market/Requester: >>>> >>>> PostgreSQL P-Team >>>> >>>> 3.3. Business Justification: >>>> >>>> We want to reduce the amount of resources needed to support and sustain >>>> old versions of PostgreSQL. We also want to keep in sync with the >>>> PostgreSQL communitys EOL policy i.e. we don't want to >>>> be in the position of having a PostgreSQL version in Solaris that is >>>> no longer supported and maintained by the community. >>>> >>>> 3.4. Competitive Analysis: >>>> >>>> N/A >>>> >>>> 3.5. Opportunity Window/Exposure: >>>> >>>> This needs to coincide with the integration of 8.4, so as to ensure >>>> that only the latest 2 versions of PostgreSQL are available/supported, >>>> and all previous versions are EOF/EOL. >>>> >>>> 3.6. How will you know when you are done?: >>>> >>>> The project will be complete when the announcement is made in >>>> a patch release of Solaris and when 8.2 is removed from a minor >>>> release of Solaris. >>>> >>>> 4. Technical Description: >>>> 4.1. Details: >>>> >>>> This project will create a release note in a Patch release of >>>> Solaris (i.e. Solaris 10 Update). It will also remove all 8.2 >>>> packages from a Minor release of Solaris (i.e., Solaris 11). >>>> >>>> The Solaris 10 Update Release Notes will be updated with the >>>> following text: >>>> >>>> PostgreSQL version 8.2 may no longer be supported >>>> in a future release. >>>> >>>> 4.2. Bug/RFE Number(s): >>>> >>>> N/A >>>> >>>> 4.3. In Scope: >>>> >>>> 4.4. Out of Scope: >>>> >>>> 4.5. Interfaces: >>>> >>>> Imported Interfaces: >>>> Interface Stability Citation >>>> --------- --------- ---------- >>>> N/A >>>> >>>> Exported Interfaces: >>>> Interface Classification Comments >>>> --------------------- --------------- ------------------------ >>>> SUNWpostgr-82-client Obsolete Package >>>> SUNWpostgr-82-contrib Obsolete Package >>>> SUNWpostgr-82-devel Obsolete Package >>>> SUNWpostgr-82-docs Obsolete Package >>>> SUNWpostgr-82-jdbc Obsolete Package >>>> SUNWpostgr-82-libs Obsolete Package >>>> SUNWpostgr-82-pl Obsolete Package >>>> SUNWpostgr-82-server Obsolete Package >>>> SUNWpostgr-82-server-data-root Obsolete Package >>>> SUNWpostgr-82-tcl Obsolete Package >>>> /lib/svc/method/postgresql Obselete SMF method script >>>> /usr/postgres/8.2 Obsolete Installation location >>>> /usr/postgres/8.2/bin Obsolete Executable location >>>> /usr/postgres/8.2/doc Obsolete Documentation >>>> /usr/postgres/8.2/etc Obsolete Config files >>>> /usr/postgres/8.2/include Obsolete Header files >>>> /usr/postgres/8.2/jdbc Obsolete JDBC driver >>>> /usr/postgres/8.2/lib Obsolete Shared libraries >>>> /usr/postgres/8.2/man Obsolete Manual pages >>>> /usr/postgres/8.2/share Obsolete Localized message files >>>> /usr/share/man/man5/postgres_82.5 Obselete Sun specific man page >>>> /var/postgres/8.2 Obselete Default db location >>>> /var/svc/manifest/application/database/postgresql.xml Obselete SMF manifest file >>>> >>>> Also deleted are all files under /usr/postgres/8.2/* (too numerous to >>>> list here). >>>> >>>> 4.6. Doc Impact: >>>> >>>> Comprehensive documentation was included with the product. This will >>>> be removed. The only other documentation impact will be the delivery >>>> of the release note (see section 4.1). >>>> >>>> 4.7. Admin/Config Impact: >>>> >>>> None. >>>> >>>> 4.8. HA Impact: >>>> >>>> N/A >>>> >>>> 4.9. I18N/L10N Impact: >>>> >>>> N/A >>>> >>>> 4.10. Packaging & Delivery: >>>> >>>> The packages listed in 4.5 will be deleted and will not be >>>> included with the first release of Solaris 11. However, note >>>> that they have been delivered with SXDE; I don't know if this >>>> will require us to go through the full EOF process. >>>> >>>> Users upgrading from Solaris 10 who are running a database >>>> under PostgreSQL 8.1 or 8.2 will have to use the upgrade solution we >>>> included with the 8.3 integration to upgrade to 8.3 or 8.4. >>>> >>>> 4.11. Security Impact: >>>> >>>> No impact. >>>> >>>> 4.12. Dependencies: >>>> >>>> Depends on the integration of 8.4 >>>> >>>> 5. Reference Documents: >>>> >>>> All material associated with the original ARC case to integrate >>>> PostgreSQL 8.1 can be found at: >>>> http://sac.sfbay.sun.com/LSARC/2005/515/ >>>> >>>> Material associated with the ARC case to integrate PostgreSQL >>>> 8.2 can be found at: >>>> http://sac.sfbay.sun.com/LSARC/2006/655/ >>>> >>>> Material associated with the ARC case to integrate PostgreSQL >>>> 8.3 can be found at >>>> http://sac.sfbay.sun.com/LSARC/2008/004 >>>> >>>> PostgreSQL 8.3 information can be found at: >>>> http://www.postgresql.org/ >>>> >>>> 6. Resources and Schedule: >>>> 6.1. Projected Availability: >>>> >>>> Can be done immediately after 8.4 is integrated. >>>> >>>> 6.2. Cost of Effort: >>>> >>>> Minimal; just removal of a component. >>>> >>>> 6.3. Cost of Capital Resources: >>>> >>>> None. >>>> >>>> 6.4.1. Consolidation or Component Name: >>>> >>>> SFW >>>> >>>> 6.4.3. Type of CPT Review and Approval expected: >>>> >>>> FastTrack >>>> >>>> 6.4.4. Project Boundary Conditions: >>>> >>>> N/A >>>> >>>> 6.4.5. Is this a necessary project for OEM agreements: >>>> >>>> No >>>> >>>> 6.4.6. Notes: >>>> >>>> 6.4.7. Target RTI Date/Release: >>>> >>>> ASAP after the community releases 8.4. >>>> >>>> 6.4.8. Target Code Design Review Date: >>>> 6.4.9. Update approval addition: >>>> >>>> 6.5. ARC review type: >>>> >>>> FastTrack >>>> >>>> 6.6. ARC Exposure: >>>> >>>> open >>>> >>>> 6.6.1. Rationale: >>>> >>>> N/A >>>> >>>> 7. Prototype Availability: >>>> 7.1. Prototype Availability: >>>> >>>> N/A >>>> >>>> 7.2. Prototype Cost: >>>> >>>> N/A >> -- >> Jim Gates Sun Microsystems >> Nashua, NH, USA http://sun.com/postgresql > -- Jim Gates Sun Microsystems Nashua, NH, USA http://sun.com/postgresql From John.Fischer@sun.com Thu Oct 2 09:35:18 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 m92GZH9s015102 for ; Thu, 2 Oct 2008 09:35:17 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m92GYr3j009578 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Fri, 3 Oct 2008 00:35:16 +0800 (SGT) 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 <0K8400G0DE2P3000@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 09:35:13 -0700 (PDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K8400C1FE2O8990@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 09:35:12 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m92GZCeE005009 for ; Thu, 02 Oct 2008 16:35:12 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K8400F01DDCKY00@mail-amer.sun.com> (original mail from John.Fischer@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 10:35:12 -0600 (MDT) Received: from 129.145.154.66 ([129.145.154.66]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K8400J25E2IJF90@mail-amer.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 10:35:07 -0600 (MDT) Date: Thu, 02 Oct 2008 09:35:06 -0700 From: John Fischer Subject: Re: EOF of PostgreSQL 8.2 in Solaris [LSARC/2008/616 timeout 10/08/2008] In-reply-to: <48E4EF8E.2040602@sun.com> Sender: John.Fischer@sun.com To: James Gates Cc: lsarc-ext@sun.com Reply-to: John.Fischer@sun.com Message-id: <1222965306.50059.2928.camel@sr1-umpk-16> MIME-version: 1.0 X-Mailer: Ximian Evolution 1.4.6.301 Content-type: text/plain; charset=ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48E2A4EC.6000607@sun.com> <1222819176.50059.479.camel@sr1-umpk-16> <48E4D732.2000408@sun.com> <1222961406.50059.2859.camel@sr1-umpk-16> <48E4EF8E.2040602@sun.com> Status: RO Content-Length: 13983 James, Actually, if you get the patch produced well before the GA of the Update then the patch will be included in the release and automatically installed. So anyone using the Update will see or have a chance of seeing the automatic message. John On Thu, 2008-10-02 at 08:58, James Gates wrote: > Oh, I see. We would have to modify the community code to include a call > to syslog(3), but I don't see that as too much of a problem. > > I think the biggest issue is, for S10, this can only be issued in a > patch. So we're relying on people who don't read release notes to keep > up to date with the latest patches. Therefore there's a good chance that > no one will ever see the syslog message, but since it's technically > feasible to do, we will do it. > > > John Fischer wrote: > > James, > > > > The application warning message would be from the previous > > release. So you would need to patch an application or applications > > with the message for Solaris 10. This should occur at the > > same time as the release notes are updated. The reason why > > this is desirable is because many of the those using the > > product might not even see the release notes or read a > > man page. That is why the EOF procedures document found > > at: > > > > http://sac.sfbay/cgi-bin/bp.cgi?NAME=Obsolete-EOF.bp > > > > suggests: > > > > Where technically feasible, inclusion in the release > > where the interface is declared Obsolete of a warning > > mechanism if the interface is used. > > > > It goes on to suggest a log warning could be used. > > > > So in the Patch release of Solaris where the release note > > will be updated it would be really good and if technically > > feasible to also have a mechanism for the EOF message to > > be declared automatically. When I've Obsoleted an interface > > I have done a popup dialog because I deal with GUIs. However, > > in this case a system log or to standard error would be sufficient. > > > > Thanks, > > > > John > > > > On Thu, 2008-10-02 at 07:14, James Gates wrote: > >> John Fischer wrote: > >>> James, > >>> > >>> Sounds like a well thought out plan. > >>> > >>> Does it make sense to add to the release note which > >>> version is recommended to migrate to in the future release? > >>> So perhaps the release note might say something like: > >>> > >>> PostgreSQL version 8.2 may no longer be supported > >>> in a future release of Solaris. You may want to > >>> migrate to PostgresSQL version 8.4. > >>> > >> That makes sense. We can even include in the message a reference to our > >> upgrade tool. > >>> Also is there a command that should spit out the same > >>> message? > >> We hadn't planned to do this. > >> > >> All the 8.2 binaries are found in /usr/postgres/8.2/bin. I had > >> anticipated that this would no longer exist after an upgrade, since all > >> 8.2 packages will be removed. > >> > >> There are 3 popular commands in /usr/postgres/8.2/bin that a user would > >> call to create, start or connect to a PostgreSQL database. > >> > >> I suppose when we remove the 8.2 packages from Nevada, we could add 3 > >> scripts to /usr/postgres/8.2/bin in the 8.3 packages that print the > >> above message. And when we EOF 8.3, add similar scripts to 8.4, etc. > >>> Thanks, > >>> > >>> John > >>> > >>> > >>> On Tue, 2008-09-30 at 15:15, James Gates wrote: > >>>> I'm sponsoring this on behalf of the PostgreSQL P-Team. Timeout is set > >>>> for 8th October. Attached is a copy of the proposal, which can also be > >>>> found in the case directory. > >>>> > >>>> -- > >>>> Jim Gates Sun Microsystems > >>>> Nashua, NH, USA http://sun.com/postgresql > >>>> > >>>> ______________________________________________________________________ > >>>> Template Version: @(#)onepager.txt 1.35 07/11/07 SMI > >>>> Copyright 2007 Sun Microsystems > >>>> > >>>> 1. Introduction > >>>> 1.1. Project/Component Working Name: > >>>> EOF of PostgreSQL 8.2 in Solaris > >>>> > >>>> 1.2. Name of Document Author/Supplier: > >>>> James Gates > >>>> > >>>> 1.3. Date of This Document: > >>>> 09/30/08 > >>>> > >>>> 1.3.1. Date this project was conceived: > >>>> 09/17/08 > >>>> > >>>> 1.4. Name of Major Document Customer(s)/Consumer(s): > >>>> 1.4.1. The PAC or CPT you expect to review your project: > >>>> > >>>> Database PAC > >>>> > >>>> 1.4.2. The ARC(s) you expect to review your project: > >>>> > >>>> LSARC > >>>> > >>>> 1.4.3. The Director/VP who is "Sponsoring" this project: > >>>> > >>>> Chris.Armes@sun.com > >>>> > >>>> 1.4.4. The name of your business unit: > >>>> > >>>> Software/RPE > >>>> > >>>> 1.5. Email Aliases: > >>>> 1.5.1. Responsible Manager: Thulasinathan.P@sun.com > >>>> 1.5.2. Responsible Engineer: James.Gates@sun.com > >>>> 1.5.3. Marketing Manager: Wei-Chen.Chiu@sun.com > >>>> 1.5.4. Interest List: sun-postgres-pteam@sun.com > >>>> > >>>> [In the following, "8.1", "8.2", "8.3" or "8.4" without qualification > >>>> refer to the corresponding PostgreSQL version.] > >>>> > >>>> 2. Project Summary > >>>> 2.1. Project Description: > >>>> > >>>> Solaris currently includes versions 8.1, 8.2 & 8.3. It is expected > >>>> that the community will release 8.4 in Dec 2008. We plan to integrate > >>>> it into Solaris shortly after community release. > >>>> > >>>> This project proposes to announce the EOF for 8.2 in a patch > >>>> release of Solaris (i.e. Solaris 10 Update) and removal of the > >>>> feature in a minor release of Solaris (i.e. Solaris 11). > >>>> > >>>> The intention of the PostgreSQL EOL policy approved by the DB PAC > >>>> is to provide active support for the latest 2 versions integrated > >>>> with Solaris. Hence the release and integration of 8.4 triggers the > >>>> EOF & EOL of 8.2. > >>>> > >>>> Note that the ARC case to EOF 8.1 was approved on 01/15/2008 > >>>> (LSARC/2008/005). > >>>> > >>>> 2.2. Risks and Assumptions: > >>>> > >>>> If Solaris 11 is shipped without 8.2 it would force customers > >>>> still running this version to upgrade PostgreSQL immediately > >>>> if they upgrade their O/S. They might even decide not to > >>>> upgrade because of this (although I think this is unlikely). > >>>> Those customers who must continue to run 8.2 can still visit the > >>>> community website and download the freely available software. > >>>> > >>>> There is also a risk that some other Sun products depend on > >>>> 8.2; we need to ensure that these are upgraded to at least 8.3. > >>>> I have verified that no other packages in the SFWNV > >>>> consilidation are listed as depending on any of the PostgreSQL > >>>> 8.2 packages. > >>>> > >>>> 3. Business Summary > >>>> > >>>> 3.1. Problem Area: > >>>> > >>>> The PostgreSQL community release a new major version approximately > >>>> once every year. For various reasons, we need to encourage customers > >>>> to upgrade to newer versions when they become available. > >>>> > >>>> 3.2. Market/Requester: > >>>> > >>>> PostgreSQL P-Team > >>>> > >>>> 3.3. Business Justification: > >>>> > >>>> We want to reduce the amount of resources needed to support and sustain > >>>> old versions of PostgreSQL. We also want to keep in sync with the > >>>> PostgreSQL communitys EOL policy i.e. we don't want to > >>>> be in the position of having a PostgreSQL version in Solaris that is > >>>> no longer supported and maintained by the community. > >>>> > >>>> 3.4. Competitive Analysis: > >>>> > >>>> N/A > >>>> > >>>> 3.5. Opportunity Window/Exposure: > >>>> > >>>> This needs to coincide with the integration of 8.4, so as to ensure > >>>> that only the latest 2 versions of PostgreSQL are available/supported, > >>>> and all previous versions are EOF/EOL. > >>>> > >>>> 3.6. How will you know when you are done?: > >>>> > >>>> The project will be complete when the announcement is made in > >>>> a patch release of Solaris and when 8.2 is removed from a minor > >>>> release of Solaris. > >>>> > >>>> 4. Technical Description: > >>>> 4.1. Details: > >>>> > >>>> This project will create a release note in a Patch release of > >>>> Solaris (i.e. Solaris 10 Update). It will also remove all 8.2 > >>>> packages from a Minor release of Solaris (i.e., Solaris 11). > >>>> > >>>> The Solaris 10 Update Release Notes will be updated with the > >>>> following text: > >>>> > >>>> PostgreSQL version 8.2 may no longer be supported > >>>> in a future release. > >>>> > >>>> 4.2. Bug/RFE Number(s): > >>>> > >>>> N/A > >>>> > >>>> 4.3. In Scope: > >>>> > >>>> 4.4. Out of Scope: > >>>> > >>>> 4.5. Interfaces: > >>>> > >>>> Imported Interfaces: > >>>> Interface Stability Citation > >>>> --------- --------- ---------- > >>>> N/A > >>>> > >>>> Exported Interfaces: > >>>> Interface Classification Comments > >>>> --------------------- --------------- ------------------------ > >>>> SUNWpostgr-82-client Obsolete Package > >>>> SUNWpostgr-82-contrib Obsolete Package > >>>> SUNWpostgr-82-devel Obsolete Package > >>>> SUNWpostgr-82-docs Obsolete Package > >>>> SUNWpostgr-82-jdbc Obsolete Package > >>>> SUNWpostgr-82-libs Obsolete Package > >>>> SUNWpostgr-82-pl Obsolete Package > >>>> SUNWpostgr-82-server Obsolete Package > >>>> SUNWpostgr-82-server-data-root Obsolete Package > >>>> SUNWpostgr-82-tcl Obsolete Package > >>>> /lib/svc/method/postgresql Obselete SMF method script > >>>> /usr/postgres/8.2 Obsolete Installation location > >>>> /usr/postgres/8.2/bin Obsolete Executable location > >>>> /usr/postgres/8.2/doc Obsolete Documentation > >>>> /usr/postgres/8.2/etc Obsolete Config files > >>>> /usr/postgres/8.2/include Obsolete Header files > >>>> /usr/postgres/8.2/jdbc Obsolete JDBC driver > >>>> /usr/postgres/8.2/lib Obsolete Shared libraries > >>>> /usr/postgres/8.2/man Obsolete Manual pages > >>>> /usr/postgres/8.2/share Obsolete Localized message files > >>>> /usr/share/man/man5/postgres_82.5 Obselete Sun specific man page > >>>> /var/postgres/8.2 Obselete Default db location > >>>> /var/svc/manifest/application/database/postgresql.xml Obselete SMF manifest file > >>>> > >>>> Also deleted are all files under /usr/postgres/8.2/* (too numerous to > >>>> list here). > >>>> > >>>> 4.6. Doc Impact: > >>>> > >>>> Comprehensive documentation was included with the product. This will > >>>> be removed. The only other documentation impact will be the delivery > >>>> of the release note (see section 4.1). > >>>> > >>>> 4.7. Admin/Config Impact: > >>>> > >>>> None. > >>>> > >>>> 4.8. HA Impact: > >>>> > >>>> N/A > >>>> > >>>> 4.9. I18N/L10N Impact: > >>>> > >>>> N/A > >>>> > >>>> 4.10. Packaging & Delivery: > >>>> > >>>> The packages listed in 4.5 will be deleted and will not be > >>>> included with the first release of Solaris 11. However, note > >>>> that they have been delivered with SXDE; I don't know if this > >>>> will require us to go through the full EOF process. > >>>> > >>>> Users upgrading from Solaris 10 who are running a database > >>>> under PostgreSQL 8.1 or 8.2 will have to use the upgrade solution we > >>>> included with the 8.3 integration to upgrade to 8.3 or 8.4. > >>>> > >>>> 4.11. Security Impact: > >>>> > >>>> No impact. > >>>> > >>>> 4.12. Dependencies: > >>>> > >>>> Depends on the integration of 8.4 > >>>> > >>>> 5. Reference Documents: > >>>> > >>>> All material associated with the original ARC case to integrate > >>>> PostgreSQL 8.1 can be found at: > >>>> http://sac.sfbay.sun.com/LSARC/2005/515/ > >>>> > >>>> Material associated with the ARC case to integrate PostgreSQL > >>>> 8.2 can be found at: > >>>> http://sac.sfbay.sun.com/LSARC/2006/655/ > >>>> > >>>> Material associated with the ARC case to integrate PostgreSQL > >>>> 8.3 can be found at > >>>> http://sac.sfbay.sun.com/LSARC/2008/004 > >>>> > >>>> PostgreSQL 8.3 information can be found at: > >>>> http://www.postgresql.org/ > >>>> > >>>> 6. Resources and Schedule: > >>>> 6.1. Projected Availability: > >>>> > >>>> Can be done immediately after 8.4 is integrated. > >>>> > >>>> 6.2. Cost of Effort: > >>>> > >>>> Minimal; just removal of a component. > >>>> > >>>> 6.3. Cost of Capital Resources: > >>>> > >>>> None. > >>>> > >>>> 6.4.1. Consolidation or Component Name: > >>>> > >>>> SFW > >>>> > >>>> 6.4.3. Type of CPT Review and Approval expected: > >>>> > >>>> FastTrack > >>>> > >>>> 6.4.4. Project Boundary Conditions: > >>>> > >>>> N/A > >>>> > >>>> 6.4.5. Is this a necessary project for OEM agreements: > >>>> > >>>> No > >>>> > >>>> 6.4.6. Notes: > >>>> > >>>> 6.4.7. Target RTI Date/Release: > >>>> > >>>> ASAP after the community releases 8.4. > >>>> > >>>> 6.4.8. Target Code Design Review Date: > >>>> 6.4.9. Update approval addition: > >>>> > >>>> 6.5. ARC review type: > >>>> > >>>> FastTrack > >>>> > >>>> 6.6. ARC Exposure: > >>>> > >>>> open > >>>> > >>>> 6.6.1. Rationale: > >>>> > >>>> N/A > >>>> > >>>> 7. Prototype Availability: > >>>> 7.1. Prototype Availability: > >>>> > >>>> N/A > >>>> > >>>> 7.2. Prototype Cost: > >>>> > >>>> N/A > >> -- > >> Jim Gates Sun Microsystems > >> Nashua, NH, USA http://sun.com/postgresql > > > > -- > Jim Gates Sun Microsystems > Nashua, NH, USA http://sun.com/postgresql From John.Plocher@sun.com Thu Oct 2 10:35:51 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 m92HZpiv018514 for ; Thu, 2 Oct 2008 10:35:51 -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 m92HZlnH002927 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 2 Oct 2008 10:35:50 -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 <0K8400A0DGVPVS00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 11:35:49 -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 <0K84007GFGVO2Z60@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 11:35:48 -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 m92HZmaJ025562 for ; Thu, 02 Oct 2008 10:35:48 -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 <0K8400H01GGK3A00@fe-sfbay-10.sun.com> (original mail from John.Plocher@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 10:35:48 -0700 (PDT) Received: from wp668.SFBay.Sun.COM ([129.146.226.219]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K8400E30GVNECB0@fe-sfbay-10.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 02 Oct 2008 10:35:48 -0700 (PDT) Date: Thu, 02 Oct 2008 10:35:46 -0700 From: John Plocher Subject: Re: EOF of PostgreSQL 8.2 in Solaris [LSARC/2008/616 timeout 10/08/2008] In-reply-to: <48E4D732.2000408@sun.com> Sender: John.Plocher@sun.com To: James Gates Cc: John.Fischer@sun.com, lsarc-ext@sun.com Message-id: <48E50672.70207@Sun.Com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48E2A4EC.6000607@sun.com> <1222819176.50059.479.camel@sr1-umpk-16> <48E4D732.2000408@sun.com> User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) Status: RO Content-Length: 424 James Gates wrote: > There are 3 popular commands in /usr/postgres/8.2/bin that a user would > call to create, start or connect to a PostgreSQL database. > > I suppose when we remove the 8.2 packages from Nevada, we could add 3 > scripts to /usr/postgres/8.2/bin in the 8.3 packages that print the > above message. And when we EOF 8.3, add similar scripts to 8.4, etc. Maybe just 1 script, with symlinks :-) -John From boyd-adamson@usa.net Thu Oct 2 15:28:30 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 m92MSR6B001157 for ; Thu, 2 Oct 2008 15:28:30 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m92MSOM1019163; Thu, 2 Oct 2008 15:28:24 -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 <0K840060LUFBVN00@nwk-avmta-2.sfbay.sun.com>; Thu, 02 Oct 2008 15:28:23 -0700 (PDT) Received: from sca-ea-mail-1.sun.com ([192.18.43.24]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K8400427UFBFE50@nwk-avmta-2.sfbay.sun.com>; Thu, 02 Oct 2008 15:28:23 -0700 (PDT) Received: from relay24.sun.com (relay24.sun.com [192.12.251.74] (may be forged)) by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m92MI94O019838; Thu, 02 Oct 2008 22:28:23 +0000 (GMT) Received: from mms23es.mms.us.syntegra.com ([150.143.232.50] [150.143.232.50]) by relay24i.sun.com with ESMTP id BT-MMP-4845401; Thu, 02 Oct 2008 22:28:22 +0000 (Z) Received: from relay24.sun.com (relay24.sun.com [192.12.251.74]) by mms23es.mms.us.syntegra.com with ESMTP id BT-MMP-152783718; Thu, 02 Oct 2008 22:28:22 +0000 (Z) Received: from ipmail04.adl2.internode.on.net ([203.16.214.57] [203.16.214.57]) by relay24i.sun.com with ESMTP id BT-MMP-45179229; Thu, 02 Oct 2008 22:28:22 +0000 (Z) Received: from boydadamson.com (HELO maelstrom.tactio.lan) ([150.101.157.138]) by ipmail04.adl2.internode.on.net with ESMTP; Fri, 03 Oct 2008 07:57:29 +0930 Received: from maelstrom.tactio.lan ([10.11.12.4] helo=maelstrom) by maelstrom.tactio.lan with esmtp (Exim 4.69) (envelope-from ) id 1KlWdq-0001Nh-Kq; Fri, 03 Oct 2008 08:27:26 +1000 Date: Fri, 03 Oct 2008 08:27:26 +1000 From: Boyd Adamson Subject: Re: EOF of PostgreSQL 8.2 in Solaris [LSARC/2008/616 timeout 10/08/2008] In-reply-to: <48E4D96B.1010604@sun.com> To: James Gates Cc: Bill Walker , John.Fischer@sun.com, lsarc-ext@sun.com Message-id: MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEADvl5EiWZZ2K/2dsb2JhbACBcbBJFItpgWo X-IronPort-AV: E=Sophos;i="4.33,353,1220193000"; d="scan'208";a="219257907" X-Antispam: No, score=0.0/5.0, scanned in 0.174sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <48E2A4EC.6000607@sun.com> <1222819176.50059.479.camel@sr1-umpk-16> <48E2C670.2020800@Sun.COM> <48E4D96B.1010604@sun.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (usg-unix-v) Status: RO Content-Length: 414 James Gates writes: > Bill Walker wrote: >> >> Just curious, but isn't SunMC still using 8.1.4? Are plans in place >> over there to use the same version/packages? >> > Yes, but we're working with them to help migrate. We can't remove 8.1 > from Nevada until 1 year after EOF announcement, or until SunMC have > migrated (whichever is sooner). Surely that's "whichever is later"? Boyd