Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
References: <000d01cb9163$22ac2d10$68048730$@thetaphi.de>
 <AANLkTimw-HECMVU2imASbmouE+n8VikH_Z8KXPMd6pFy@mail.gmail.com>
 <D199B09F-7CF0-4E4A-8DF7-702EF4F80F41@apache.org>
 <4CFB2B3F.4050308@gmail.com>
 <D0725770-DB77-461E-91F7-FEF0661AD793@jpl.nasa.gov>
 <AANLkTimajfRoXD9KH6=beAYd3+kxbVCMs4rEOhOpd10u@mail.gmail.com>
 <7669DC24-B379-472B-B551-CCA9B441D502@jpl.nasa.gov>
 <AANLkTim0fYkEWQX3BbMsR39OaRfpurdcwtxwZ1GFW=Aw@mail.gmail.com>
In-Reply-To: <AANLkTim0fYkEWQX3BbMsR39OaRfpurdcwtxwZ1GFW=Aw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: Changes Mess
From: Uwe Schindler <uwe@thetaphi.de>
Date: Mon, 06 Dec 2010 15:51:41 +0100
To: dev@lucene.apache.org
Message-ID: <f241fd8e-ab50-4b24-a4b6-5b16ba29d679@email.android.com>

If you have full control on your Jira installation, you could define a custom field named "changes entry and credits". This field could be used for a report.

But we have no separate installation to have all control.

Uwe


"Robert Muir" <rcmuir@gmail.com> schrieb:

>On Sun, Dec 5, 2010 at 10:35 PM, Mattmann, Chris A (388J)
><chris.a.mattmann@jpl.nasa.gov> wrote:
>> Hi Robert,
>>
>> True, JIRA isn't a perfect solution for this matter, but works good
>enough usually since many times (especially with prodding) those same
>users who report the bugs are those that report the JIRA issues.
>>
>
>I agree it would be more ideal if we always tried to encourage users
>to open JIRA issues.
>But we cant "force" users to do this, you know and we should still fix
>it + give them credit if they just don't reply at all.
>
>I also agree with some of what Steven is saying: here's a concrete
>example from 2.9.4 (just released):
>
>CHANGES file:
>LUCENE-2658: Exceptions while processing term vectors enabled for
>multiple fields could lead to invalid ArrayIndexOutOfBoundsExceptions.
>
>JIRA description:
>LUCENE-2658: TestIndexWriterExceptions random failure: AIOOBE in
>ByteBlockPool.allocSlice
>
>So you see the story, i hit a random test failure and just opened an
>issue describing that the test randomly failed.
>Mike then went and fixed it and wrote up a CHANGES.txt entry thats
>significantly better to the users.
>
>In order for us to use JIRA here, we would have to do a lot of
>JIRA-editing and re-organizing I think, and probably create a lot of
>unnecessary issues.
>
>For example, on some issues that I felt should only be "fixed" in
>later releases, i wanted to still backport "documentation only" fixes
>to 2.9.4/3.0.3.
>Documentation only fixes aren't very risky and at least alert users to
>the issue... but it would be bad if CHANGES.txt made them think it was
>actually fixed!
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>For additional commands, e-mail: dev-help@lucene.apache.org

--
Uwe Schindler
H.-H.-Meier-Allee 63, 28213 Bremen
http://www.thetaphi.de

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