Return-Path: X-Original-To: apmail-cocoon-dev-archive@www.apache.org Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0F3F9DBF3 for ; Thu, 13 Dec 2012 10:25:51 +0000 (UTC) Received: (qmail 34489 invoked by uid 500); 13 Dec 2012 10:25:50 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 34207 invoked by uid 500); 13 Dec 2012 10:25:50 -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 34182 invoked by uid 99); 13 Dec 2012 10:25:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Dec 2012 10:25:49 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [78.134.5.44] (HELO rovere.tirasa.net) (78.134.5.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Dec 2012 10:25:43 +0000 Received: from localhost (localhost [127.0.0.1]) by rovere.tirasa.net (Postfix) with ESMTP id 2D92A186E84 for ; Thu, 13 Dec 2012 11:25:21 +0100 (CET) X-Virus-Scanned: amavisd-new at tirasa.net Received: from rovere.tirasa.net ([127.0.0.1]) by localhost (rovere.tirasa.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id amcIcjWkKQ-O for ; Thu, 13 Dec 2012 11:25:15 +0100 (CET) Received: from [192.168.0.2] (mogano.tirasa.net [192.168.0.2]) by rovere.tirasa.net (Postfix) with ESMTPSA id 5DE93186D81 for ; Thu, 13 Dec 2012 11:25:15 +0100 (CET) Message-ID: <50C9AD0B.2090109@apache.org> Date: Thu, 13 Dec 2012 11:25:15 +0100 From: =?ISO-8859-1?Q?Francesco_Chicchiricc=F2?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: [DISCUSS] C3 tagging X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Hi all, I'd like to understand whether there is any particular reason behind the way tags are created for C3 releases [1] by a dedicated script [2], instead of letting the maven-release-plugin manage tags by following the standard layout. If there are no objections, I'd propose to empower the maven-release-plugin for managing the whole C3 release process; I would also like to update and move [3] to a dedicate page on the website. All this to be proven and refined for upcoming 3.0.0-beta-1 release. WDYT? Regards. [1] https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/ [2] https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/BEFORE_COCOON3-105/svn-release-tags.sh [3] https://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/RELEASE_HOWTO.txt -- Francesco Chicchiricc� ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/