Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0D7531060E for ; Tue, 29 Oct 2013 15:00:28 +0000 (UTC) Received: (qmail 75783 invoked by uid 500); 29 Oct 2013 14:59:54 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 75658 invoked by uid 500); 29 Oct 2013 14:59:42 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 75542 invoked by uid 99); 29 Oct 2013 14:59:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Oct 2013 14:59:35 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of curtisr7@gmail.com designates 209.85.160.53 as permitted sender) Received: from [209.85.160.53] (HELO mail-pb0-f53.google.com) (209.85.160.53) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Oct 2013 14:59:30 +0000 Received: by mail-pb0-f53.google.com with SMTP id up7so8012495pbc.40 for ; Tue, 29 Oct 2013 07:59:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=QbLV7QXxahlXyF7d44hFg7IzX13SowZJe653ABtoq6w=; b=ACytA/iDEJAxJ6OEwVla0TDth+6+Qxv+SaRHIeYN9SvEPYKrzP+46rgQOH1CHNhbAg LCJL4HH4QEs1UMbK2G3TeiC8/EE94CWuxQv3uBEzxyFe04MBnZyc32qYQVHyQx37UCze Qg3PJVTQJ/kKShEQh1PHA4vrEzgPO7Da3LTxEom4q2fCSFl2dmzSKyEAgHj+Iwqye3Ee 1LyoYW9fRsJrqYPVXNNxp+qoJt95eaugBNHpjjPUKtVe09lG4+Uioj7LEyvsSMcz9XDX KxGOE4AyXjrJkUTVu+YE/DKYmfYzygDw6TTOVUpOvmchBlZdEk7UWvMrMCC9CVIbYFvI lFnA== MIME-Version: 1.0 X-Received: by 10.68.254.132 with SMTP id ai4mr27101697pbd.51.1383058750358; Tue, 29 Oct 2013 07:59:10 -0700 (PDT) Received: by 10.68.4.5 with HTTP; Tue, 29 Oct 2013 07:59:10 -0700 (PDT) In-Reply-To: <1383058050.16841.YahooMailNeo@web28903.mail.ir2.yahoo.com> References: <1383035268.86520.YahooMailNeo@web28904.mail.ir2.yahoo.com> <1383058050.16841.YahooMailNeo@web28903.mail.ir2.yahoo.com> Date: Tue, 29 Oct 2013 09:59:10 -0500 Message-ID: Subject: Re: release preparations for 2.3.0 From: Rick Curtis To: dev@openjpa.apache.org, Mark Struberg Content-Type: multipart/alternative; boundary=047d7b2e0a1184cde704e9e27529 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b2e0a1184cde704e9e27529 Content-Type: text/plain; charset=ISO-8859-1 Sure, I get that case... but I'd bet that many of the JIRAs that are unresolved, with no committed code, and fix version of 2.3.0 haven't really been resolved. On Tue, Oct 29, 2013 at 9:47 AM, Mark Struberg wrote: > hmmm I'd let the fix version. > This often happens if a fix got applied committed as part of another JIRA. > But still the reported issue got fixed. > The same happens if a unit test shows that the reported bug already got > fixed in the meantime. > > Imo those cases should still get tagged as 'fixed in ...' > > LieGrue, > strub > > > > > ----- Original Message ----- > > From: Kevin Sutter > > To: dev@openjpa.apache.org > > Cc: > > Sent: Tuesday, 29 October 2013, 15:30 > > Subject: Re: release preparations for 2.3.0 > > > > Yes, you are probably right. If no code has been committed any release or > > trunk, then there should be no "fix version", just the "affects > > version". > > > > > > > > On Tue, Oct 29, 2013 at 9:16 AM, Rick Curtis wrote: > > > >> Should we just remove the 'Fix Version/s' attribute if it is set to > > 2.3.0 > >> when no code has been committed? ie : > >> https://issues.apache.org/jira/browse/OPENJPA-1988 > >> > >> > >> On Tue, Oct 29, 2013 at 9:10 AM, Kevin Sutter > > wrote: > >> > >> > Thanks, Mark. I just got rid of three of the JIRAs from your query > > and > >> > working on another one with Jody. There may be others that should or > >> could > >> > be cleaned up, but I picked the easy ones first... :-) I hate to > > just > >> > carry over JIRAs from one release to another to another... Some of > > these > >> > should probably just be returned as "won't fix" (similar > > to the ones I > >> did > >> > already). I'll let others take a run through the query and see if > > there > >> > are candidates. > >> > > >> > Thanks! > >> > Kevin > >> > > >> > > >> > On Tue, Oct 29, 2013 at 3:27 AM, Mark Struberg > > > >> wrote: > >> > > >> > > Hi! > >> > > > >> > > Could you please walk through the unresolved OpenJPA-2.3.0 issues > > and > >> set > >> > > those who you doubt should be fixed already to > > 'resolved'? > >> > > > >> > > > >> > > > >> > > >> > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENJPA%20AND%20fixVersion%20%3D%20%222.3.0%22%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > >> > > > >> > > I hope to start with the actual release task either tonight or > > tomorrow > >> > > morning. > >> > > Means I gonna send another mail in 15 hours and then will > > transit the > >> > > still unresolved issues to 2.4.0. > >> > > > >> > > There is also another thing which I like to do: finally get rid > > of all > >> > the > >> > > bad tabs and unused imports in 2.3.x and trunk. > >> > > See OPENJPA-2200. I will _not_ change any lines other than tabs > > and > >> > unused > >> > > imports so far. > >> > > Patches should thus still apply fine even across older versions. > >> > > > >> > > LieGrue, > >> > > strub > >> > > > >> > > >> > >> > >> > >> -- > >> *Rick Curtis* > >> > > > -- *Rick Curtis* --047d7b2e0a1184cde704e9e27529--