Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 209.85.220.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=KVcJu4KbgK3cJd+uA1fsrsNnsWNPqbhfWiP/qkdZgjHFWF2XFyMFz2PslbRn1RL2fZ
         qlmqWz9qqVo0Zzm38Gumtcdxk1wKQ9OArF1Sig3GyZUHDdFJyUuRhKXIP+oe5UIFFcwV
         Ib6b3UNQrcCvGJtUUVuDrci7UrjiS/zvLqxNc=
MIME-Version: 1.0
In-Reply-To: <BANLkTinwfVDKEsLjfL3AMbGUnR4_hYHWvQ@mail.gmail.com>
References: <BANLkTi=wQ1J2UtHEXd+vmoJvb-fNz_2mMQ@mail.gmail.com>
	<4DE94A18.8070900@gmail.com>
	<BANLkTi=9ORTjPin-n9ET1QYP=EXkCK=w0A@mail.gmail.com>
	<BANLkTinpyjYC+yfzijcpRYftLXYrYHKkDA@mail.gmail.com>
	<4DE99BC2.5080806@gmail.com>
	<BANLkTinwfVDKEsLjfL3AMbGUnR4_hYHWvQ@mail.gmail.com>
Date: Sat, 4 Jun 2011 19:08:06 +0100
Message-ID: <BANLkTimsudD-5gUnJ16Bt11=k2u=RoSMzw@mail.gmail.com>
Subject: Re: JIRA report usefulness (was: [VOTE] Release Commons NET 3.0.1
 based on RC3)
From: sebb <sebbaz@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 4 June 2011 18:33, Henri Yandell <flamefew@gmail.com> wrote:
> On Fri, Jun 3, 2011 at 7:43 PM, Phil Steitz <phil.steitz@gmail.com> wrote=
:
>> On 6/3/11 7:27 PM, Henri Yandell wrote:
>>> On Fri, Jun 3, 2011 at 2:09 PM, Simone Tripodi <simonetripodi@apache.or=
g> wrote:
>>>>> I think that is also best practice - resolve when fixed in SVN,
>>>>> close when fix version is released.
>>>>>
>>>> I couldn't agree more!!! +1!
>>> I just close directly. The resolve then close is a workflow waiting
>>> for a reason :)
>>
>> The reason is that until a release has been cut including the fix,
>> it is still a problem faced by users. =A0Just fixing in svn should not
>> close the issue.
>
> Not a good enough reason imo. If 'Resolved' was called 'Committed' and
> 'Closed' was 'Released', then maybe. As it is we'll have a workflow
> that is meaningless to anyone but the committers; and they can already
> look at whether the fix version has been released or not.

Well, we could just document how we use Resolved and Closed.

> If Atlassian hadn't made the mistake of a 2 stage resolution as their
> default; we wouldn't be looking for a solution. As they did everyone
> (not just here, it's a JIRA anti-pattern) tries to apply a workflow to
> the Resolve/Close step.
>
> Hen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

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