Return-Path: Delivered-To: apmail-repository-archive@www.apache.org Received: (qmail 4736 invoked from network); 7 Aug 2006 00:06:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Aug 2006 00:06:23 -0000 Received: (qmail 69560 invoked by uid 500); 7 Aug 2006 00:06:22 -0000 Delivered-To: apmail-repository-archive@apache.org Received: (qmail 69487 invoked by uid 500); 7 Aug 2006 00:06:22 -0000 Mailing-List: contact repository-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: repository@apache.org List-Id: Delivered-To: mailing list repository@apache.org Received: (qmail 69476 invoked by uid 99); 7 Aug 2006 00:06:22 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Aug 2006 17:06:22 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [217.12.11.96] (HELO smtp007.mail.ukl.yahoo.com) (217.12.11.96) by apache.org (qpsmtpd/0.29) with SMTP; Sun, 06 Aug 2006 17:06:22 -0700 Received: (qmail 65973 invoked from network); 7 Aug 2006 00:06:00 -0000 Received: from unknown (HELO ?192.168.1.30?) (reinhard?poetz@62.178.239.20 with plain) by smtp007.mail.ukl.yahoo.com with SMTP; 7 Aug 2006 00:06:00 -0000 Message-ID: <44D683E5.4070303@apache.org> Date: Mon, 07 Aug 2006 02:05:57 +0200 From: Reinhard Poetz User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: repository@apache.org Subject: Re: Cocoon 2.2 M1 artifacts in m2-ibiblio-rsync-repository References: <1a5b6c410608031241i5af605ffu8dfbae8c00a610e0@mail.gmail.com> <9e3862d80608061633p6ba9148et8ab0a7a017ebc2b2@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Wendy Smoak wrote: > On 8/6/06, Brett Porter wrote: > >> This isn't a matter of agreeing or disagreeing. If you put something >> into the sync repository, it is the same as putting it into /dist/. >> You've said "we've released these files, push them out to the world". >> >> It's becoming all too frequent that stuff gets pushed there and then >> done again when a problem is noticed. I would like to see us >> cataloguing the reasons this occurs and doing whatever we can to avoid >> it in future. > > We need a release staging repository. And then we need a reliable way > to "promote" artifacts from staging to ibiblio-rsync, so that the > repository metadata is correct. > > I can't see how any project with a reasonably complex build could > release straight to the rsynced repo. And definitely not the ones > (like Struts) that use a test build stage, where a version is tagged > and built, then voted on later. It's nice if everything works > perfectly the first time, but all you have to do is forget to enable a > profile, or have a connection drop, and you have to re-build. > > What do you think? I agree here. We (the Cocoon community) came to the same conclusions. -- Reinhard P�tz Independent Consultant, Trainer & (IT)-Coach {Software Engineering, Open Source, Web Applications, Apache Cocoon} web(log): http://www.poetz.cc -------------------------------------------------------------------- ___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de