Return-Path: 
 <commons-dev-return-97873-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org
Received: (qmail 22568 invoked from network); 5 Jan 2007 20:26:19 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 5 Jan 2007 20:26:18 -0000
Received: (qmail 80826 invoked by uid 500); 5 Jan 2007 20:26:23 -0000
Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org
Received: (qmail 80740 invoked by uid 500); 5 Jan 2007 20:26:22 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 80729 invoked by uid 99); 5 Jan 2007 20:26:22 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jan 2007 12:26:22 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of jak-commons-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
Received: from [80.91.229.2] (HELO ciao.gmane.org) (80.91.229.2)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jan 2007 12:26:11 -0800
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1H2vdD-0001jC-Qf
	for commons-dev@jakarta.apache.org; Fri, 05 Jan 2007 21:25:39 +0100
Received: from vpn.rauser-ag.com ([62.157.169.229])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <commons-dev@jakarta.apache.org>; Fri, 05 Jan 2007 21:25:39 +0100
Received: from joerg.heinicke by vpn.rauser-ag.com with local (Gmexim 0.1
 (Debian))
        id 1AlnuQ-0007hv-00
        for <commons-dev@jakarta.apache.org>; Fri, 05 Jan 2007 21:25:39 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: commons-dev@jakarta.apache.org
From: Joerg Heinicke <joerg.heinicke@gmx.de>
Subject: Re: [all] Jira reporting
Date: Fri, 5 Jan 2007 20:25:24 +0000 (UTC)
Lines: 29
Message-ID: <loom.20070105T115330-402@post.gmane.org>
References: <31cc37360701021402p6664f74cpf4d6da49af793e78@mail.gmail.com>
  <loom.20070103T093544-651@post.gmane.org>
  <31cc37360701030914g6bd7479ex87670c69da637b0b@mail.gmail.com>
 <16d6c6200701030920w788c36b1u16ad98a6b62bcf87@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: main.gmane.org
User-Agent: Loom/3.14 (http://gmane.org/)
X-Loom-IP: 62.157.169.229 (Mozilla/5.0 (Windows; U; Windows NT 5.0; de;
 rv:1.8.1) Gecko/20061010 Firefox/2.0)
Sender: news <news@sea.gmane.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Martin Cooper <martinc <at> apache.org> writes:

> > > Any exact targetting for unresolved issues will lead to "this
> > > issues hasn't made it into the latest release, we try to get it into the
> > > next one" mails polluting the mailing lists without nearly any additional
> > > value.
> >
> > I think that is a good thing as it means someone is looking at that
> > issue each release and deciding that it won't go in that release. If
> > it keeps getting punted all the time then someone can ask if it's ever
> > going to happen.
> 
> This is exactly why we moved to something like what Hen is proposing for
> Struts. We had oodles of issues just sitting there with no indication of
> when, if ever, they were likely to be fixed, and no indication of whether
> anyone was committed to looking at them. Once you start versioning the
> issues, you get the beginnings of a roadmap rather than just a bucket of
> issues.

Ok, that's a point. Cocoon does indeed suffer from this as well. But I guess in
Cocoon changing this would just not work (or end in 300 "issue version
re-addressed" mails per release). For the maintenance branch the development is
much less targeted as it is more or less only project-driven, i.e. an issues
that a committer needs on his current project gets handled rapidly. Other issues
are mostly done on demand or on request. For littler projects or projects with
less chaotic project management (which I like much though :)) the above might
indeed be useful.

Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org