Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 69798 invoked from network); 16 Aug 2007 15:21:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Aug 2007 15:21:22 -0000 Received: (qmail 80796 invoked by uid 500); 16 Aug 2007 15:21:19 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 80758 invoked by uid 500); 16 Aug 2007 15:21:19 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 80749 invoked by uid 99); 16 Aug 2007 15:21:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Aug 2007 08:21:19 -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 jta@bristowhill.com designates 66.75.162.137 as permitted sender) Received: from [66.75.162.137] (HELO ms-smtp-05.socal.rr.com) (66.75.162.137) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Aug 2007 15:21:15 +0000 Received: from [192.168.1.100] (cpe-76-88-116-210.san.res.rr.com [76.88.116.210]) by ms-smtp-05.socal.rr.com (8.13.6/8.13.6) with ESMTP id l7GFKof9029905 for ; Thu, 16 Aug 2007 08:20:51 -0700 (PDT) Message-ID: <46C46B52.4090600@bristowhill.com> Date: Thu, 16 Aug 2007 08:20:50 -0700 From: "Jean T. Anderson" Reply-To: jta@bristowhill.com User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc3 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: What fix version to use for fixes merged to the 10.3 branch? References: <46BF22DF.90905@amberpoint.com> <46C06C65.40902@sun.com> <46C0DFD5.6020601@sbcglobal.net> <46C1EF56.1020909@sun.com> <54ac72d70708141631y6f5635d4s3e0b6b08a13ab762@mail.gmail.com> <46C31FC1.9080801@sun.com> <46C32ABD.3050005@apache.org> <46C33ABD.8060904@sun.com> <46C33CA0.9000007@sbcglobal.net> <46C3460A.4080500@sun.com> <54ac72d70708151353m93cf6a3y14fe47d4e9e72252@mail.gmail.com> <46C3707A.5080203@sbcglobal.net> <46C3AC61.1020307@bristowhill.com> <46C45CDF.9060304@apache.org> In-Reply-To: <46C45CDF.9060304@apache.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Virus-Checked: Checked by ClamAV on apache.org Daniel John Debrunner wrote: > Jean T. Anderson wrote: > >> The only >> people who are supposed to know about such packages are the people >> following the dev list (or searching its archives) and thus aware of the >> conditions placed on the package." >> >> So it's fine to post the location of a snapshot to the mail list so >> users can test it. > > By "the mail list" you mean "the derby-dev mail list", right? So "users" > can test it but only if they follow derby-dev list. If I remember the discussions last year on legal-discuss (?), I think strong opinions were stated that it should be on the dev list (I'd have to go back and look). But there would be no problem with posting to the user list about snapshots being available for review and "check the traffic on the dev list" (perhaps providing the URL to make it easy for users to check the dev list). What was really clear was there should be no pointers to the snapshots on the web site -- and we did a swift cleanup on the web site to both remove links to snapshots and also increase the separation of dev and user info. One example of the latter was we moved information about source from the Download tab to the Community tab. -jean