Quite interesting discussion!
Some notes from my point of view:
1+ for resolved -> close workflow, in this case everybody has a chance to
see whats fixed and properly untested (walkthrough), it would be a kind of
checklist which parts of an upcoming release should be tested.
However, Do you know, that its possible to change workflows in JIRA [1],
[2]. With this in mind, and hopefully its possible to define
project specific workflows, it would be a great to define transition
between different states:
My favorite would look like this:
open --> close (wont fix)
open --> close (its not a bug)
open --> close (duplicate to)
open --> resolve (fixed and the fixed version will be set if the release
is identified, properly more than once if applied to different branches)
resolve --> close (kind of check "Yes it works")
resolve --> reopen (Hmm, sorry good try but bug is not fixed)
Is it possible do administrate the JIRA instance (properly for both,
geoserver and geotools but independently)
Cheers,
Frank
[1] http://www.slideshare.net/GoAtlassian/c6-mastering-jira-workflows
2012/5/25 Ben Caradoc-Davies <[email protected]>
> +1. I think we need to ditch the use of fixVersion for end-user
> pleading. Only set fixVersion if you or your team are working on the
> issue and are committed to including it in that release. This is
> Justin's use-case of a developer asking a release manager to wait for a
> particular fix.
>
> On 24/05/12 16:24, Andrea Aime wrote:
> > From that point of view I'd wish that people stopped flagging the
> > "fix for" unless there is something backing the work to fix the issue
>
> --
> Ben Caradoc-Davies <[email protected]>
> Software Engineer
> CSIRO Earth Science and Resource Engineering
> Australian Resources Research Centre
>
>
> ------------------------------------------------------------------------------
> 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
>
------------------------------------------------------------------------------
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
