Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-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 1A48910027 for ; Mon, 14 Oct 2013 05:45:43 +0000 (UTC) Received: (qmail 91081 invoked by uid 500); 14 Oct 2013 05:45:40 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 90704 invoked by uid 500); 14 Oct 2013 05:45:39 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 90696 invoked by uid 99); 14 Oct 2013 05:45:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Oct 2013 05:45:37 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of flamefew@gmail.com designates 209.85.128.171 as permitted sender) Received: from [209.85.128.171] (HELO mail-ve0-f171.google.com) (209.85.128.171) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Oct 2013 05:45:32 +0000 Received: by mail-ve0-f171.google.com with SMTP id c14so436457vea.16 for ; Sun, 13 Oct 2013 22:45:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=uBwvsSxaiXgyYrfO+I2/e8dPd3J+wmQMl+FGdhNOwjk=; b=1GGKV3a+Lqhmr8dKj9mw3Mbo+yRJ4ZmRZCjM6rLWo9j7EPQ4G61GWe4LNJcLXjQ5Zh 1zezDPRMTZZg//gMLnQEpfbPNzEqJs9l4UG5txXBNXTaXS6WB2TKWoH6rxGk2e0g0dVG /vAreYDvVuzKDrWOt+LoXZYUWNGyOp19PEhkSgIz1LW6KyU5LucsrS5ZMvkdmkyYbzVw 0/QcN3Id1By0AQL/mgc4NdtVkPWIib/gD8qmeodQmJLPjebkrDtKeLnD+1VTjdjEk6/i t+MzC8L3oBpXhElJ+58vBaWBtu+HzBuP8dB5hEGkIevxTZkV+o6MloDNlsNrKonN6iNj 6VnA== MIME-Version: 1.0 X-Received: by 10.52.64.143 with SMTP id o15mr27967820vds.16.1381729511960; Sun, 13 Oct 2013 22:45:11 -0700 (PDT) Received: by 10.52.72.9 with HTTP; Sun, 13 Oct 2013 22:45:11 -0700 (PDT) In-Reply-To: <525B6F33.4040204@gmail.com> References: <525B6F33.4040204@gmail.com> Date: Sun, 13 Oct 2013 22:45:11 -0700 Message-ID: Subject: Re: [DISCUSS] Why is releasing such a pain and what can we do to make it easier? From: Henri Yandell To: Commons Developers List Content-Type: multipart/alternative; boundary=20cf30776153bc74ba04e8acf892 X-Virus-Checked: Checked by ClamAV on apache.org --20cf30776153bc74ba04e8acf892 Content-Type: text/plain; charset=ISO-8859-1 On Sun, Oct 13, 2013 at 9:12 PM, Phil Steitz wrote: > > > Could be I am misunderstanding the proposal. Do you mean a) RM is > not obligated to do anything but tag a release and create tarballs > or b) RM should just be trusted to "do the right thing" in getting > stuff published and other other PMC members should review / help > with "post-release" stuff ad hoc? Could be b) could work as long as > we collectively agree to keep an eye on things / review stuff > outside of RC votes. > Officially, b). But, I do think a) is a very interesting stance. Let's say I think Lang 3.2 is ready and call a vote. Currently the community is going to vote -1 simply because I'm not interested in doing lots of bells and whistles. However, svn tag LANG_3.2 We're done. Release is done and the only step potentially missing is svn export, tar cf, put in a web directory for download. Now those who care about having a source tarball in some special place (it's not in svn somewhere right?) and all the other things can go do them. I know I've sat and kept JIRA's updated for projects who weren't doing so, why is a maven repo or whatever else any different? I'm being extreme, but I think it's an interesting challenge for our 'everyone must meet this bar' approach. The more we raise the bar, the more star systems slip through our fingers. Erm. Something like that :) Hen --20cf30776153bc74ba04e8acf892--