Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 714 invoked from network); 19 Mar 2007 18:56:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Mar 2007 18:56:30 -0000 Received: (qmail 3074 invoked by uid 500); 19 Mar 2007 18:56:38 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 2868 invoked by uid 500); 19 Mar 2007 18:56:38 -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 2859 invoked by uid 99); 19 Mar 2007 18:56:38 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Mar 2007 11:56:38 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of mcintyre.a@gmail.com designates 209.85.132.240 as permitted sender) Received: from [209.85.132.240] (HELO an-out-0708.google.com) (209.85.132.240) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Mar 2007 11:56:28 -0700 Received: by an-out-0708.google.com with SMTP id c25so1172676ana for ; Mon, 19 Mar 2007 11:56:08 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZdzEGiTz5g3V8iU2fTPAwCbk7ZfNG+FrSGALwH+BQ+5Ct2RA3k4G07D/heR6ocLBSwzvuaSzZrMhSJ7pS7pkU+zPnGI7ayv4ah+9S63Zv59r85RKQVVfeJfZJWFQH4+i/+C2GeZnWlGTyEV3hGVNiKOMtqtq9HZJxIubmlNdAkY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=DJqun5f7652aee29xXAHGERWRJQ84DJt0buTTwaJ1UudOVzJzopbdtj38Rq/WZ25HNqFof9j7N+XOFAfG2fqbq9gLVHAOXSH7RVgHOHG/LztUPWDSVm9nKVGic8py9cHa7an+fqmWZ5E8c4hhX5T8A8khoIi9pLnrvN7jfOZtK8= Received: by 10.100.191.5 with SMTP id o5mr4128650anf.1174330568091; Mon, 19 Mar 2007 11:56:08 -0700 (PDT) Received: by 10.100.34.20 with HTTP; Mon, 19 Mar 2007 11:56:08 -0700 (PDT) Message-ID: <54ac72d70703191156i1ad8f57am66252a3d5fa195d4@mail.gmail.com> Date: Mon, 19 Mar 2007 11:56:08 -0700 From: "Andrew McIntyre" To: derby-dev@db.apache.org Subject: Re: Are we still setting Fix Version to 10.3.0.0? In-Reply-To: <45FEDAE3.20803@amberpoint.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45FEDAE3.20803@amberpoint.com> X-Virus-Checked: Checked by ClamAV on apache.org On 3/19/07, Bryan Pendleton wrote: > I think we recently made the decision that the next release > will be called 11.0, but I see that in Jira we have both > 10.3 and 11.0. > > When fixing an issue in the trunk, how do we want to handle > fields such as Fix Version? I've been setting them to 10.3, > but maybe that's going to cause confusion? I would say set it to 10.3 for now, since that's what the trunk is currently set to. 10.3 can always be merged with 11.0 later if that does end up being the next release version. andrew