Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 10560 invoked from network); 9 Jan 2008 08:13:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Jan 2008 08:13:41 -0000 Received: (qmail 37111 invoked by uid 500); 9 Jan 2008 08:13:29 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 37031 invoked by uid 500); 9 Jan 2008 08:13:29 -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 37020 invoked by uid 99); 9 Jan 2008 08:13:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jan 2008 00:13:29 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [88.198.46.98] (HELO indoqa.com) (88.198.46.98) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jan 2008 08:13:04 +0000 Received: from [192.168.1.32] (chello062178239020.5.15.vie.surfer.at [62.178.239.20]) by indoqa.com (Postfix) with ESMTP id 8FB3C254841 for ; Wed, 9 Jan 2008 09:30:56 +0100 (CET) Message-ID: <47848214.2090700@apache.org> Date: Wed, 09 Jan 2008 09:13:08 +0100 From: Reinhard Poetz User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Question about sample site in trunk References: <4781D575.60301@dslextreme.com> <315091D3-B792-4B79-AFF6-89105D6361F2@reverycodes.com> <47831974.7050906@dslextreme.com> <4783D2BE.5030403@apache.org> <4784516C.8040704@gmx.de> In-Reply-To: <4784516C.8040704@gmx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Joerg Heinicke wrote: > On 08.01.2008 14:45, Grzegorz Kossakowski wrote: > >> We were not shipping samples because samples should depend on released >> artifacts, only. Anyway, I >> agree that we need to find a way for distribution of our samples. >> >> However, I wonder how we will treat them? As official released >> packages with version number schemes, >> etc.? >> I would like to go with just creating zip archives containing source >> code of all our samples that >> depend on released artifacts. We would update such archive from time >> to time, as need occurs. I >> don't think we need any more formalization. WDYT? > > I don't know if it is put in question but IMO we still need an actual > Cocoon 2.2 release which is more than core but also includes as many > blocks as possible (the ones converted and working). Where is the > problem to include all these blocks with their samples? http://cocoon.apache.org/2.2/blocks/ contains a list of all blocks that have been released so far and could go into an ordinary Cocoon release. For all other blocks there hasn't even been a Maven release yet. If somebody wants to see any of them included, it has to be made ready for a release (make sure that it works and meets all formal requirements; documentation would be nice but IMO not a requirement). -- Reinhard P�tz Managing Director, {Indoqa} GmbH http://www.indoqa.com/en/people/reinhard.poetz/ Member of the Apache Software Foundation Apache Cocoon Committer, PMC member, PMC Chair reinhard@apache.org _________________________________________________________________________