Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 59257 invoked from network); 12 May 2008 12:10:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 May 2008 12:10:14 -0000 Received: (qmail 49250 invoked by uid 500); 12 May 2008 12:10:14 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 49194 invoked by uid 500); 12 May 2008 12:10:14 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 49183 invoked by uid 99); 12 May 2008 12:10:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 May 2008 05:10:14 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rickmcg@gmail.com designates 64.233.166.182 as permitted sender) Received: from [64.233.166.182] (HELO py-out-1112.google.com) (64.233.166.182) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 May 2008 12:09:27 +0000 Received: by py-out-1112.google.com with SMTP id a25so1937713pyi.11 for ; Mon, 12 May 2008 05:09:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; bh=JrYcJLbOeg4g62rVP0T1uTtTWjK1nnZ9hsOJoU/UbwM=; b=klwR5ohuivY2qLrD0G/kshCFd+9yr1g/R27qdwOEdjV7cozAuXr1dPiirazJ2n03BfeZ4K3JfYmqziiXiqWFhARMlfWF2i2jYdJVpSNyCJBOgjJ/ZeEORpSszMo1K38O1YI1YDtxQxtey/ijZIQT1g4YJfrisOSxE4gXiDNEiRk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=eGhd50+PSrD7vfsv6Jfs/43vLj2tVmJ3TFoYO2/AP1kMbRoZ0FmLWRsgxvCNYbv1uKrSEhPlGlEfa9o8L3ePbnJu0A3Qbcg2aBxJ2rDTnbKFR8Dnp2mbmxCauX09l+w4kEqs1C5o6EyNjaIYF8aGu6IpGnfH5HDesYUSeCHLVzU= Received: by 10.35.17.14 with SMTP id u14mr13773052pyi.61.1210594181836; Mon, 12 May 2008 05:09:41 -0700 (PDT) Received: from ?192.168.1.101? ( [68.191.49.248]) by mx.google.com with ESMTPS id x48sm10509865pyg.34.2008.05.12.05.09.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 12 May 2008 05:09:40 -0700 (PDT) Message-ID: <48283383.7070705@gmail.com> Date: Mon, 12 May 2008 08:09:39 -0400 From: Rick McGuire Reply-To: rickmcg@gmail.com User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Geronimo Dev Subject: [DISCUSS] do additional artifacts need to be removed as part of the release process. Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org This is an issue that came up with the vote on 1.0 Yoko release. The new release process detailed at http://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+release+process generates a bunch of extra artifacts that are .md5 and sha1 signatures for the .asc files. So, for every jar file, you will get a .asc file, plus additional asc.md5 and asc.sha1 files. In our old release process, one of the steps was to erase all of the *.asc.* files before staging the release for a vote. Now that this is done automatically by using the plugins, these extra artifacts get included, and even get staged to the repos. For example, see the artifacts that got published for the last javamail release, which was the most recent release to use this process: http://repo1.maven.org/maven2/org/apache/geronimo/javamail/geronimo-javamail_1.4_provider/1.4/ Should our release process include the step to delete these additional files? Or should this be something that should/could be fixed in the plugin so that these extraneous files don't get included accidentally? Rick