Hey Ben,
On Tue, May 22, 2012 at 8:09 PM, Ben Caradoc-Davies <
[email protected]> wrote:
> On 22/05/12 21:56, Justin Deoliveira wrote:
>
>> As far as I can tell it is mostly Ben that by default closes the issue.
>>
>
> I usually only close issues I reported, or those confirmed fixed by my
> team or partners, or where I am manually synchronising codehaus with my
> group's private Jira (used for iteration planning).
>
> An alternative practice is that used in my group's private Jira; closing
> is a management review activity and is not in general performed by
> developers. This is might not be appropriate for an open source project as
> we have limited management resources.
>
> In a nutshell, let us follow the Jira definition: "Resolved — A Resolution
> has been identified or implemented, and this issue is awaiting verification
> by the reporter. From here, issues are either 'Reopened' or are 'Closed'."
>
Right it makes sense, again my issue is that closing issues before the
associated fixCersion is released is a real pain when realeasing in jira. I
will bring this up as a topic for discussion in our next IRC meeting.
>
> So closed means verified complete by the reporter (or some other
> responsible party).
>
> Kind regards,
>
> --
> Ben Caradoc-Davies <[email protected]>
> Software Engineer
> CSIRO Earth Science and Resource Engineering
> Australian Resources Research Centre
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
