On Tue, May 22, 2012 at 9:01 PM, Ben Caradoc-Davies <
[email protected]> wrote:
> Oh, I see the problem: an issue might even have correctly set fixVersion
> at the time, be closed, and we might add an extra release or skip a beta,
> rendering existing fixVersions incorrect, forcing reopening of the issues.
> I think this is one for Monday's meeting.
>
Exactly.
>
> This is becoming cumbersome. How about using fixVersion for branches only
> and deducing the changes with some clever JQL? Does JQL support joins? This
> way madness lies ...
Come on... is closing issues before a release really that important?
>
>
> On 23/05/12 10:41, Justin Deoliveira wrote:
>
>> 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.
>>
>
> --
> 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
