Issue 7363: Dependency on D+C FTF (lwccm-ftf) Source: Zuehlke Engineering (Mr. Frank Pilhofer, fpilhofer2008(at)gmail.com) Nature: Uncategorized Issue Severity: Summary: Lightweight CCM replaces CCM's Packaging and Deployment chapter with the "Deployment and Configuration of Component-based Distributed Applications" (D+C) specification, and thus Lightweight CCM cannot be finalized before D+C. I propose to defer this issue to a second FTF, to be resolved by the availability of D+C. Resolution: Revised Text: Actions taken: May 19, 2004: received issue Discussion: End of Annotations:===== ubject: Dependency on D+C FTF Date: Wed, 19 May 2004 09:52:37 -0400 Thread-Topic: Dependency on D+C FTF Thread-Index: AcQ9qIqSrbiUYgfVQl610JoXf6hcBQ== From: "Pilhofer, Frank" To: Cc: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id i4JDsdun008363 Lightweight CCM replaces CCM's Packaging and Deployment chapter with the "Deployment and Configuration of Component-based Distributed Applications" (D+C) specification, and thus Lightweight CCM cannot be finalized before D+C. I propose to defer this issue to a second FTF, to be resolved by the Subject: RE: Issue 7363 question Date: Wed, 26 May 2004 14:08:30 -0400 Thread-Topic: Issue 7363 question Thread-Index: AcRDTHJYz0mNpx7xT8WRy7vro9TZmg== From: "Pilhofer, Frank" To: Cc: "Andreas Wolf" A question about the deferral of Issue 7363: Does this mean we *keep* the .old. CCM deployment structure or that we do not have *anything* about deployment, until the D FTF is finished? The intention is for Lightweight CCM to use the Deployment and Configuration specification for the deployment of applications. However, since D+C is still in FTF, and is going to recharter, the same applies to Lightweight CCM because of this dependency. My intention is to recharter a Lightweight CCM 2004 FTF at the upcoming OMG meeting in Orlando, with only this one issue to take care of. The schedule of the second FTF will match the D+C FTF schedule. In the hopefully unlikely case that D+C fails to be finalized, we can resolve the issue by replacing the reference to D+C with CCM's original Packaging and Deployment chapter. Frank availability of D+C.