commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: JIRA report usefulness (was: [VOTE] Release Commons NET 3.0.1 based on RC3)
Date Sat, 04 Jun 2011 18:08:06 GMT
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.org>
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.  Just 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


Mime
View raw message