Hi,
recently I've started to see a trend of more jira issues being marked as
"blockers".
Blocker is, or should be, "end of the world, attend to immediately" type of
issue, e.g., a build breakage
on the official build server, something that blocks every developer, but I
see it used
as "it's a blocker _for me_" instead, which I believe is misuse.
I know Jira has a definition here:
http://jira.codehaus.org/secure/ShowConstantsHelp.jspa?decorator=popup#PriorityLevels
and this thread is also interesting:
http://lists.opencastproject.org/pipermail/matterhorn/2009-August/002038.html
Imho before setting an issue to "blocker" level you should ask youself "is
it really
blocking all developers?"
We're all extremely busy, marking a issue at such a high level looks like a
tentative
to get undeserved attention for an issue that is not actually affecting
everybody.
Of course we can discuss this and come up with a meaning other than the
usual one
if people feel strongly about it.
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
------------------------------------------------------------------------------
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
