Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 46283 invoked from network); 28 Sep 2008 20:43:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Sep 2008 20:43:10 -0000 Received: (qmail 74979 invoked by uid 500); 28 Sep 2008 20:43:07 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 74827 invoked by uid 500); 28 Sep 2008 20:43:07 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 74816 invoked by uid 99); 28 Sep 2008 20:43:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Sep 2008 13:43:07 -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 jukka.zitting@gmail.com designates 209.85.198.251 as permitted sender) Received: from [209.85.198.251] (HELO rv-out-0708.google.com) (209.85.198.251) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Sep 2008 20:42:07 +0000 Received: by rv-out-0708.google.com with SMTP id k29so1868509rvb.0 for ; Sun, 28 Sep 2008 13:42:41 -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:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ELOzxeFgnoHAHe2v9Z5KF7CnFyI+Exy3GSSATVEOwTo=; b=Sl/0lCojSyvvmy0/lrHcalCCDs93iUQnHt19ooE+uOTdPtAzOo/Wet+2YQM2YxLzoy zp4VAgpCL19XBgWRqmWwJ0h9t7GZDoNMZpfW+lV9lbZwKVWd402+gSvZqk4/0Sruna10 HM0gVRmE8KS5Sp1kJh9mOwnaYCTlOTVWJoUZ4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=MBPKBnwx7UZznAbzQqPV2Xkxok+DENPy4jjBZGyaMlPTph4amKWWgfIJ24HBp+G8Gl rbQNdNy6Zam7CFmKLSy3oPyBtw9w2wnwpf8NevtGxMiHVkDFjoNKDTLKgVREAwA3QJ/C riEs8qhJq/7iB7OcJekXRtQGKr1WFtyZjQjDQ= Received: by 10.141.156.11 with SMTP id i11mr2030704rvo.1.1222634561962; Sun, 28 Sep 2008 13:42:41 -0700 (PDT) Received: by 10.141.210.5 with HTTP; Sun, 28 Sep 2008 13:42:41 -0700 (PDT) Message-ID: <510143ac0809281342l2bbe50a2pb9c60d914552a28e@mail.gmail.com> Date: Sun, 28 Sep 2008 22:42:41 +0200 From: "Jukka Zitting" To: general@incubator.apache.org Subject: Re: On incubating releases In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <510143ac0809260541h21809939u9252426780f1b5c6@mail.gmail.com> <19e0530f0809270453t74610422ue3a28ef8faa5f1f3@mail.gmail.com> <510143ac0809270839o8ad0c75pbe6e74a075909049@mail.gmail.com> <19e0530f0809271010h3f39daaex7633c96eb3d6eb70@mail.gmail.com> <510143ac0809271045m598a27c0if1bda7495b29a6e5@mail.gmail.com> <510143ac0809281105p12c4a76cq4383a44f8fe7a8d1@mail.gmail.com> <510143ac0809281127v1868df0bp5438312cfa5e3443@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi, On Sun, Sep 28, 2008 at 9:40 PM, Matthieu Riou wrote: > On Sun, Sep 28, 2008 at 11:27 AM, Jukka Zitting wrote: >> That person would already have seen the incubating web site, the >> release notes and most likely also the README, all of which come with >> our disclaimers. > > If it came from central? Unlikely. He/she would probably get it from another > source transitively. The artifact might already be downloaded to the local repository, but how would this person know to want to add that to project B without already knowing about the incubating project? Just as easily one can come up with the unlikely scenario of project A copying a dependency jar from another Ant project without finding out more about that jar. What's the difference? > Just take it the other way around. If we push all our releases to central, > why would we still have the disclaimer on our release page? It's not > coherent. People don't just browse the central repository and decide "this jar file looks cool, I'll add a dependency to it". They find the project through some other means, normally through the website and decide to add the dependency by that information. Anyway, if (as you say) the problem is with the developer who adds the dependency to project B and not with the users of project B, then I believe there are a number of alternative solutions (putting the disclaimer inside the POM, etc.) that should better address your concerns. So far my understanding has been that the main concern is about the users of project B! BR, Jukka Zitting --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org