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.
Once we decide what is best i will document our "jira policy" in the
developer guide.
Thanks!
-Justin
--
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
