On 09/05/12 15:52, Andrea Aime wrote:
> recently I've started to see a trend of more jira issues being marked as
> "blockers".
Sorry, that sounds like me. :-)
> 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.
One word you have added here is "official". While I appreciate the work
that OpenGeo have done in providing Hudson coverage, it is not the only
build coverage for this project.
Despite several requests from me, the OpenGeo Hudson no longer builds in
a path with spaces, so does not catch the File/URL conversion build
failures I often report. These break the build on some Windows
development boxes, and can break production deployments on Windows and
other boxes in paths with spaces or internationalised paths ("Program
Files", "Documents and Settings").
There are other reasons to run an "unofficial" build bot, including
coverage of obscure modules like webservice; these are not OpenGeo's
problem. Others have run build bots to cover other JDKs. If we set one
up for Jody for OpenJDK would it be unofficial? Are only OpenGeo Hudson
failures blockers?
I don't expect the community to monitor other buildbots, but I do expect
to be able to report problems that break the build for bots or multiple
developers as blockers.
I agree that it is annoying to have many blockers. I have been trying to
fix this build all week:
http://geobuilder.arrc.csiro.au/geoserver/waterfall?show=GeoT-java15
> 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
I agree with all the Jira definitions except one: what Jira refers to as
a Priority is in fact a Severity. These are not the same thing.
> 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.
How about "Blocker" meaning that a build bot is broken or several
developers cannot build? I agree that one developer's build failure does
not constitute a blocker. In the past I have reported blockers and been
more than happy to reduce their Jira Priority when I realised that it
was only affecting a single machine.
Would it help if I went back and fixed the Priority of recent Blockers
for which temporary fixes have been committed?
Kind regards,
--
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/
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
