On Tuesday 11 August 2009 13:44:36 Michael Matz wrote:
Hi,
On Tue, 11 Aug 2009, Andreas Jaeger wrote:
Oh right, because we all know that "two weeks of silence" is _nothing_ when it comes to bugzilla.
But it would be clear who owns the task and documented what is done so far (if at all).
I think the objection here is that his is a black box and people don't know what's happening, transparency should help here,
If hermes were working as designed we would have that. The problem with Bugzilla is that you have to actively enter something to show activity, in addition to the activity itself. So, if coolo looks at a SR and deems it fine, "but not for right now", he would additionally enter comments in random bugzilla entries. Or better, he wouldn't, and rightfully so, because his time is limited. That would lead to the same questions, so bugzilla in itself wouldn't help.
Something automatic would help, as repeatedly suggested by various people (hi Lars :) ), but then it doesn't matter anymore if it was called hermes or bugzilla.
So, how shall we define the process with proper tools support? Could somebody write this up and define what we need as tool support ? and then let's make a new feature for the Build Service out of it. That way we have something good in the future, Andreas -- Andreas Jaeger, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126