Return-Path: 
 <dev-return-48003-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 82078 invoked from network); 23 Sep 2003 14:06:40 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 23 Sep 2003 14:06:40 -0000
Received: (qmail 71720 invoked by uid 500); 23 Sep 2003 14:05:40 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 71692 invoked by uid 500); 23 Sep 2003 14:05:40 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 71630 invoked from network); 23 Sep 2003 14:05:40 -0000
Received: from unknown (HELO gate1.stjude.org) (192.55.208.11)
  by daedalus.apache.org with SMTP; 23 Sep 2003 14:05:40 -0000
Received: by gate1.stjude.org; (8.9.3/1.3/10May95) id JAA631570;
 Tue, 23 Sep 2003 09:05:41 -0500 (CDT)
Received: from somewhere by smtpxd
Received: from somewhere by smtpxd
Message-ID: 
 <1E0CC447E59C974CA5C7160D2A2854EC098440@SJMEMXMB04.stjude.sjcrh.local>
From: "Hunsberger, Peter" <Peter.Hunsberger@stjude.org>
To: <dev@cocoon.apache.org>
Date: Tue, 23 Sep 2003 09:05:39 -0500
Subject: RE: on better release and version management
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-OriginalArrivalTime: 23 Sep 2003 14:05:39.0836 (UTC)
 FILETIME=[C4EF8BC0:01C381DB]
X-SEF-723560E2-3392-41F8-A983-A3F5486E94A: 1
content-class: urn:content-classes:message
Thread-Topic: on better release and version management
Thread-Index: AcOBzGLZ/2eLVn7gQGOqo+W9rV0LWgADvfGA
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Stefano Mazzocchi <stefano@apache.org> writes:

<snip>

> Instead of associating 'maturity levels' to the actual location of a=20
> block, I would state that as a 'label' attached to it, a=20
> label that the=20
> block deployer reacts to and prompt the user for action in case the=20
> block is not considered "final" by the community.
>=20
> That would:
>=20
>   1) keep the freedom to initiate as many blocks developers want
>   2) avoid the 'move things around' CVS dance
>   3) allow easy and mechanizable checking of which blocks are=20
> considered=20
> "stamped" by the cocoon community.
>=20
> so, the only thing left is to define how you get those blocks=20
> "stamped", but I think it would just require a community vote with a=20
> majority.
>=20
> Such "stamping" should be done thru the use of a digital=20
> certificate so=20
> that the block deployer can say "this is a block certified by the=20
> cocoon community as final".

Hmm, I think you don't mean "final" as in can't be touched, but more
like, "stable" or "certified as not being dangerous", or maybe
"certified as now being an official part of Cocoon"?