On Wed, May 23, 2012 at 1:47 AM, Andrea Aime
<[email protected]>wrote:
> On Tue, May 22, 2012 at 3:56 PM, Justin Deoliveira
> <[email protected]>wrote:
>
>> Hey all,
>>
>> Another jira inconsistency i notice is that some people close issues,
>> while others resolve them. The majority tend to resolve and then we do a
>> sort of batch close at a later date. As far as I can tell it is mostly Ben
>> that by default closes the issue. Not saying this is wrong at all, but i
>> would like to standardize to remove inconsistency.
>>
>> As i understand it the workflow is usually as follows. Someone opens an
>> issue. A developer works on issue and when satisfied with the fix marks it
>> as resolved. The original creator of the issue then confirms the issue is
>> fixed and marks the issue as closed.
>>
>> One issue i have with closing issues is that they can't be edited unless
>> re-opened. Which is a problem for releases, for example with fixVersions
>> that are not set. So I wonder if we should hold off on closing issues until
>> after the release has been published.
>>
>
> Works for me. I'm guilty of mass closing resolved issues, when I'm in
> "jira gardening mode", aka go through old issues and see if there is any
> that is solved, but nobody noticed, I also happen to close resolved issues
> that have had no comments for the last month or so. I can stop doing that.
>
> Totally fine with this as it happens after the release, often well after.
> As for the reporter closing the issues, I honestly see no problem with
> that, but indeed we need the developer closing the issue to adjust the "fix
> for" to match the branches the patch was committed on.
>
> Btw, when I do close a issue that is a "won't fix" or a "cannot reproduce"
> or an old issue that was resolved in the meantime, but there's no telling
> when, I just remove all the "fix for" to avoid having that issue get into
> changelogs, since it effectively represents no change.
> If we get a policy on how to handle issue closing the above practice needs
> discussion as well
>
Right, i think this makes sense too.
>
> Cheers
> Andrea
>
> --
> Ing. Andrea Aime
> GeoSolutions S.A.S.
> Tech lead
>
>
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
>
> phone: +39 0584 962313
> fax: +39 0584 962313
> mob: +39 339 8844549
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.youtube.com/user/GeoSolutionsIT
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
>
--
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
