Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 54246 invoked from network); 27 Mar 2008 11:55:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Mar 2008 11:55:01 -0000 Received: (qmail 35017 invoked by uid 500); 27 Mar 2008 11:54:59 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 34951 invoked by uid 500); 27 Mar 2008 11:54:59 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 34942 invoked by uid 99); 27 Mar 2008 11:54:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Mar 2008 04:54:59 -0700 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 [64.233.166.179] (HELO py-out-1112.google.com) (64.233.166.179) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Mar 2008 11:54:19 +0000 Received: by py-out-1112.google.com with SMTP id p76so4734100pyb.6 for ; Thu, 27 Mar 2008 04:54:29 -0700 (PDT) Received: by 10.35.10.13 with SMTP id n13mr2402618pyi.30.1206618869284; Thu, 27 Mar 2008 04:54:29 -0700 (PDT) Received: by 10.35.131.1 with HTTP; Thu, 27 Mar 2008 04:54:29 -0700 (PDT) Message-ID: Date: Thu, 27 Mar 2008 07:54:29 -0400 From: "James Carman" Sender: jcarman@carmanconsulting.com To: "Jakarta Commons Developers List" Subject: Re: [m2][PROPOSAL] Release process In-Reply-To: <25aac9fc0803270433r4122d370y9ec0bcb532df7efd@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8a81b4af0803221510v438fe3bdj198568a742f54e04@mail.gmail.com> <8a81b4af0803221934j548e002di63b029ebcff20ea@mail.gmail.com> <8a81b4af0803262330k1053184fgd3cca58003e9dabd@mail.gmail.com> <25aac9fc0803270433r4122d370y9ec0bcb532df7efd@mail.gmail.com> X-Google-Sender-Auth: 52ef6fcc87e8d260 X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Mar 27, 2008 at 7:33 AM, sebb wrote: > It should be obvious that code uploaded to a personal user directory > has not been formally released. > > If a shared repository is used then this is less obvious, and there is > a risk that users will assume that it is a release. If a shared > repository is to be used for unreleased (development) code then it > needs to be very clearly identified as such, and the repository > location should not be published to users. > It's almost like we need a two-phase commit here. We do some stuff and then ask everyone "are you okay with that?" What if we staged our releases to an SVN working copy? Then, everyone could look at it and if everyone was okay with it, we could commit the changes and that would somehow be updated in another "live" location on some periodic basis? I'm just thinking out loud here, so be gentle. :) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org