Return-Path: Delivered-To: apmail-incubator-cxf-dev-archive@locus.apache.org Received: (qmail 5403 invoked from network); 29 Aug 2007 02:13:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Aug 2007 02:13:25 -0000 Received: (qmail 66092 invoked by uid 500); 29 Aug 2007 02:13:20 -0000 Delivered-To: apmail-incubator-cxf-dev-archive@incubator.apache.org Received: (qmail 65897 invoked by uid 500); 29 Aug 2007 02:13:20 -0000 Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cxf-dev@incubator.apache.org Delivered-To: mailing list cxf-dev@incubator.apache.org Received: (qmail 65888 invoked by uid 99); 29 Aug 2007 02:13:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Aug 2007 19:13:20 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [64.79.194.121] (HELO mesa2.com) (64.79.194.121) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Aug 2007 02:13:13 +0000 Received: from [24.147.10.180] (account jdkulp HELO dilbert.boston.amer.iona.com) by mesa2.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 1218437 for cxf-dev@incubator.apache.org; Tue, 28 Aug 2007 22:12:51 -0400 From: Daniel Kulp To: cxf-dev@incubator.apache.org Subject: Reminder: set version number when resolving a JIRA issue... Date: Tue, 28 Aug 2007 22:12:49 -0400 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708282212.50083.dkulp@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Just a quick reminder, when you resolve/close a Jira issue, please make sure you set a version number on the issue. We generate the release notes from the Jira items so if the issue wasn't assigned a version, it won't appear in the release notes. We currently have 303 resolved/closed issues that don't have a version number assigned to them. That's almost a third of our total jira issue count. Anyway, if you've resolved an issue recently, could you please go back and make sure it's marked resolved for 2.0.2? Thanks! -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 daniel.kulp@iona.com http://www.dankulp.com/blog