Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 93130 invoked from network); 4 Jan 2007 23:45:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Jan 2007 23:45:20 -0000 Received: (qmail 6477 invoked by uid 500); 4 Jan 2007 23:45:25 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 6387 invoked by uid 500); 4 Jan 2007 23:45:25 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 6372 invoked by uid 99); 4 Jan 2007 23:45:25 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jan 2007 15:45:25 -0800 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 joerg.heinicke@gmx.de designates 213.165.64.20 as permitted sender) Received: from [213.165.64.20] (HELO mail.gmx.net) (213.165.64.20) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 04 Jan 2007 15:45:16 -0800 Received: (qmail invoked by alias); 04 Jan 2007 23:44:54 -0000 Received: from p549D1012.dip0.t-ipconnect.de (EHLO [192.168.178.20]) [84.157.16.18] by mail.gmx.net (mp045) with SMTP; 05 Jan 2007 00:44:54 +0100 X-Authenticated: #3483660 Message-ID: <459D91C5.7050301@gmx.de> Date: Fri, 05 Jan 2007 00:46:13 +0100 From: Joerg Heinicke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.9) Gecko/20061211 SeaMonkey/1.0.7 MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: versions in Jira References: <5186760.1167952887527.JavaMail.jira@brutus> In-Reply-To: <5186760.1167952887527.JavaMail.jira@brutus> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 X-Virus-Checked: Checked by ClamAV on apache.org On 05.01.2007 00:21, Jörg Heinicke (JIRA) wrote: > Resolution: Fixed > Fix Version/s: 2.2-dev (Current SVN) > 2.1.11-dev (current SVN) I wonder how we manage those versions. It seems to be quite strange: Issues fixed in 2.1.9: https://issues.apache.org/jira/browse/COCOON-1700 https://issues.apache.org/jira/browse/COCOON-1806 In 2.1.10: https://issues.apache.org/jira/browse/COCOON-1879 In 2.1.11-dev: https://issues.apache.org/jira/browse/COCOON-1977 It seems that both the renaming and the handling of the properties themselves are done wrongly: 1. 2.1.9-dev got correctly renamed to 2.1.9, but having 2.1.9-dev in "Affects Versions" lets it view quite strange as the bug seems to be in 2.1.9 and is fixed in that version as well. 2. For 2.1.10-dev it seems to be even worse. I guess it was directly renamed to 2.1.11-dev - which now makes all version infos in those bugs wrong. How it must be handled: 1. As soon as a bug gets fixed the "Current SVN" version MUST be removed from "Affects versions". As it is already fixed having it there is also no longer correct. 2. The X.Y.Z-dev version must be renamed to X.Y.Z after a release and a new entry created for X.Y.Z+1-dev and not the other way around. Otherwise we provide wrong information on issues in Jira. I'll fix the above for 2.1.10-dev => 2.1.11-dev. Jörg