Hi folks,
As discussed in Mondays IRC meeting i have written up some proposed guidelines for creating issues in jira, including the policy on resolving vs closing issues.
The first draft is up here:
https://github.com/jdeolive/geoserver/blob/jira_doc/doc/en/user/source/introduction/jira_howto.rst
Give it a read over and let me know what you think.
Thanks!
-Justin
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
As discussed in Mondays IRC meeting i have written up some proposed guidelines for creating issues in jira, including the policy on resolving vs closing issues.
The first draft is up here:
https://github.com/jdeolive/geoserver/blob/jira_doc/doc/en/user/source/introduction/jira_howto.rst
Give it a read over and let me know what you think.
Looks good; I like the part about setting expectations.
For reference here is the geotools page on the subject: http://docs.geotools.org/latest/userguide/welcome/support.html#issue-tracker
(The only advantage is the use of an example).
I think we should make a note (on both pages) about submitting patches with test cases. And if you are keen the option to submit a pull_request against the official github fork.
Jody
On Thu, May 31, 2012 at 3:47 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:
As discussed in Mondays IRC meeting i have written up some
proposed guidelines for creating issues in jira, including the policy on
resolving vs closing issues.The first draft is up here:
https://github.com/jdeolive/geoserver/blob/jira_doc/doc/en/user/source/introduction/jira_howto.rst
Give it a read over and let me know what you think.
Looks good; I like the part about setting expectations.
For reference here is the geotools page on the subject:
http://docs.geotools.org/latest/userguide/welcome/support.html#issue-tracker(The only advantage is the use of an example).
I think we should make a note (on both pages) about submitting patches with
test cases. And if you are keen the option to submit a pull_request against
the official github fork.
Yep, a patch that can be applied right away should be (imho)
prioritized over others.
At least that's what I normally do during weekends, only look at patches with
attachments, then sort them out so that I look first at the full ones,
then at the ones
without tests, and then at reports where the user at least decided to
attach some
extra information to reproduce. Not perfect by any means, but better than going
randomly into jira imho
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
Thanks, Justin.
Could we enhance impact by breaking it into two sections, bullet points at the top and explanatory text below? Then rather than hunting through the text, the must-know don't-annoy-Justin-and-Andrea information is at the top. I would also add in this section the recent decisions we made:
- Do not set Blocker priority on an issue unless it breaks the build on OpenGeo Hudson. [Include a link?]
- Do not set fix version until the fix is committed (or you are working on it and the fix is imminent) and the fix version(s) are known.
[Indent] * Because fix version is used to generate release changelogs, fix version is only to be used to record implemented fixes, not as an appeal for maintainer attention.
- Do not Close fixed issues unless you are the release manager and all referenced versions have been released.
[Indent] * Duplicate, Cannot Reproduce, Won't Fix and similar issues may be Closed as soon as they are Resolved; fix version must not be set on these issues.
Is there a reStructuredText markup for blinking text? 
Then the rest of the explanatory text below.
Kind regards,
Ben.
On 31/05/12 08:51, Justin Deoliveira wrote:
Hi folks,
As discussed in Mondays IRC meeting i have written up some proposed guidelines for creating issues in jira, including the policy on resolving vs closing issues.
The first draft is up here:
https://github.com/jdeolive/geoserver/blob/jira_doc/doc/en/user/source/introduction/jira_howto.rst
Give it a read over and let me know what you think.
Thanks!
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre