Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 28400 invoked from network); 11 Dec 2006 13:54:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Dec 2006 13:54:54 -0000 Received: (qmail 29601 invoked by uid 500); 11 Dec 2006 13:55:00 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 29515 invoked by uid 500); 11 Dec 2006 13:54:59 -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 List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 29497 invoked by uid 99); 11 Dec 2006 13:54:59 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO [127.0.0.1]) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Dec 2006 05:54:59 -0800 Message-ID: <457D635B.1050603@apache.org> Date: Mon, 11 Dec 2006 14:55:39 +0100 From: Carsten Ziegeler User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Cocoon-Dev , Cocoon-Users Subject: Looking for help in upcoming release X-Enigmail-Version: 0.94.1.2 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi community, the Cocoon project is working very hard to release 2.1.10 by Monday, December 18th. To meet this goal -- which clearly will benefit all users -- we need some *specific* QA (quality assurance) input from the user community. While we believe that the current development version of 2.1.10 is stable, we would like to prove this by our users. To help, here's what you need to do: 1. Update your local subversion repository to the *latest* 2.1.10 branch version from subversion. (http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1-X) 2. ./build.[sh|bat] clean 3. ./build.[sh\bat] 4. Assure that you use the same JDK for running Cocoon that you also used for building and start Cocoon by ./cocoon.[sh|bat] 5. Test *all* samples. Hit each and every sample page from links beginning at http://localhost:8888/samples/ 6. Report back on the Cocoon dev list on your findings, good or bad. 7. Make sure you describe your test environment: Platform and JVM, including version numbers. 8. If you find problems, be specific about the problem description: what page, what error, etc. 9. If you can provide a patch/info to fix the problem, even better. You can also test your Cocoon 2.1.9 applications with the latest version to check if everything is still working fine. What we do *not* need: Please do not submit requests for XYZ features, dreams, etc. Please save these ideas for future versions. Of course, you are welcome to start an own thread for this on the dev list as well. Thanks. The Cocoon Team Carsten -- Carsten Ziegeler - Chief Architect http://www.s-und-n.de http://www.osoco.org/weblogs/rael/