On Wed, May 9, 2012 at 8:02 PM, Ben Caradoc-Davies <
[email protected]> wrote:
> On 09/05/12 21:52, Justin Deoliveira wrote:
>
>> First when I think blocker I think blocker for users, not developers. So
>> the first question i would ask when filing an issue is "is it likely a
>> user will actually run into this issue?".
>>
>
> Sorry, I disagree with this; I am with Andrea (and the Jira definitions)
> on this one. The concept of a blocker is enmeshed with the test-driven
> development principle of not committing on a broken build except to fix
> that build. Because no developers should be committing or releasing,
> development is blocked.
Fair enough. Was just sharing what my unofficial though process is when
filing an issue and admitedly never verified it against a formal
definition. I think the jira definitions make sense too.
>
>
> --
> 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/
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
