From dev-return-67078-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Mon Nov 01 18:29:06 2004 Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 5801 invoked from network); 1 Nov 2004 18:29:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 1 Nov 2004 18:29:05 -0000 Received: (qmail 44724 invoked by uid 500); 1 Nov 2004 18:28:47 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 44531 invoked by uid 500); 1 Nov 2004 18:28:45 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 44475 invoked by uid 99); 1 Nov 2004 18:28:44 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=DNS_FROM_RFC_ABUSE X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [217.12.11.34] (HELO smtp003.mail.ukl.yahoo.com) (217.12.11.34) by apache.org (qpsmtpd/0.28) with SMTP; Mon, 01 Nov 2004 10:28:44 -0800 Received: from unknown (HELO ?62.46.166.161?) (reinhard?poetz@62.46.166.161 with plain) by smtp003.mail.ukl.yahoo.com with SMTP; 1 Nov 2004 18:28:41 -0000 Message-ID: <41868056.8060908@yahoo.de> Date: Mon, 01 Nov 2004 19:28:38 +0100 From: Reinhard Poetz User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Switching rhino implementation Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I'm going to integrate the new Rhino+cont implementation in the next few days and plan to support the old and the new implementation, at least in 2.1. I wonder ... 1. What do we want to call the new implementation (I mean the language name in ). a.) call the new implementation "javascript" and tell our users that if they have problems they can use "javascript-legacy" or some other alternative name for the old implementation? If so, shouldn't I wait for 2.1.6 and do the integration then? b.) keep "javascript" as the name of the old implementation and find a new name for the new implementation? 2. If we deprecate the old flowscript implementation in 2.1 - do we have to keep it in 2.2 or can I remove it? I would wait with switching to the new flowscript implementation until the release of 2.1.6 Then we have a few months to test it in branch and trunk and if everything goes well I would deprecate the old one and rename it to "javascript-legacy" and the new impl should be the default language. In 2.2 I would remove the old implementation completly. WDOT? -- Reinhard