[opensuse-buildservice] Use Bugzilla to report build service package bugs + requests ?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, the subject line says it all ;) Is it an option to use Novell's Bugzilla to have people report defects and requests about packages from/for the openSUSE Build Service ? Any reasons we couldn't do that ? If it's OK, what would have to be done ? Whom would we need to poke about it ? (and as for "why would you want to do that", well, IMO it would be easier to track bugs and requests than respectively nothing and a page on the wiki) cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser@skynet.be> <guru@unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGR3dHr3NMWliFcXcRAkANAKCst6xMdZuDV75ZHR4NSyggmBUWKgCcChTs u7jE/sdRu3uIjliV3BW1WD4= =Wv20 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Sunday 13 May 2007 22:38:31 wrote Pascal Bleser:
Well, the subject line says it all ;)
Is it an option to use Novell's Bugzilla to have people report defects and requests about packages from/for the openSUSE Build Service ?
Any reasons we couldn't do that ?
If it's OK, what would have to be done ?
Whom would we need to poke about it ?
A component for this can be created immediately. My main problem is that I have to enter some default owner for it. This means some person who is responsible to juggle the bugs around. Of course, the best thing is to report it directly to the package/project owner, but there needs anyway someone who takes care of the rest. The Novell screening team may be a candidate, but an own openSUSE screening team might be a better choice. So, what do we need for this ? An own ml can be created easily, but who owns them ? Are there any volunteers here ? bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N�rnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Adrian Schröter schrieb:
A component for this can be created immediately.
My main problem is that I have to enter some default owner for it. This means some person who is responsible to juggle the bugs around.
Of course, the best thing is to report it directly to the package/project owner, but there needs anyway someone who takes care of the rest.
In theory you have everything you need to make it automatic. You could use a section for the buildservice and a subsection with every repo. Then you can get a maintainer for the repo. This would need interfacing buildservice with bugzilla though and therefore I don't expect that to happen soon. Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, on Montag, 14. Mai 2007, Wolfgang Rosenauer wrote:
In theory you have everything you need to make it automatic. You could use a section for the buildservice and a subsection with every repo. Then you can get a maintainer for the repo. This would need interfacing buildservice with bugzilla though and therefore I don't expect that to happen soon.
It isn't that difficult ;-) - the buildservice just needs the addition of a link which pre-fills enter_bug.cgi. If you are interested, see https://bugzilla.novell.com/show_bug.cgi?id=229213 for technical details and an example. Well, the link isn't as good as having each project as component (as proposed by you), but it's a good start. And it has a big advantage: it can be implemented very fast. Why do we still need a default assignee? Quoting Adrian (from bugzilla):
However, there will be also users who go directly to bugzilla and we do need therefore a default owner of that package component.
Regards, Christian Boltz -- No trees were killed in the sending of this message. However a large number of electrons were terribly inconvenienced. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Adrian Schröter escribió:
A component for this can be created immediately.
yes, please ;) bugzilla is already more or less used to report bug in buildservice packages.
My main problem is that I have to enter some default owner for it. This means some person who is responsible to juggle the bugs around.
assigned by default to a mailing list maybe ?
Of course, the best thing is to report it directly to the package/project owner, but there needs anyway someone who takes care of the rest.
I Disagree.. ;) bugzilla is the best tool for this.
So, what do we need for this ? An own ml can be created easily, but who owns them ? Are there any volunteers here ?
there are volunteers already, at least I screen bugs from time to time since ages (as other people does too (f.e Andreas Hanke among others))
On 2007-05-16 00:03:42 -0400, Cristian Rodriguez R. wrote:
Adrian Schröter escribió:
A component for this can be created immediately.
yes, please ;) bugzilla is already more or less used to report bug in buildservice packages.
My main problem is that I have to enter some default owner for it. This means some person who is responsible to juggle the bugs around.
assigned by default to a mailing list maybe ?
Of course, the best thing is to report it directly to the package/project owner, but there needs anyway someone who takes care of the rest.
I Disagree.. ;) bugzilla is the best tool for this.
So, what do we need for this ? An own ml can be created easily, but who owns them ? Are there any volunteers here ?
there are volunteers already, at least I screen bugs from time to time since ages (as other people does too (f.e Andreas Hanke among others))
i discussed that with pascal on irc. the better solution is imho to move that functionality into their opensuse applications site. an user adds an entry there for the missing application. packagers can add them self to the application if they start packaging it. that way we can even easily track who packages what. that said, it would be easy for them to add a view for "all packages where the packagers count is 0". I mean the idea is that every application packaged for suse is on that site, right? just my 2 cents darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (6)
-
Adrian Schröter -
Christian Boltz -
Cristian Rodriguez R. -
Marcus Rueckert -
Pascal Bleser -
Wolfgang Rosenauer