[arch-dev-public] flyspray category for supp./unsupp. community packages?
You all know we don't have a special category for community packages in our bug tracker. But why? I haven't seen any request for it until now. So far we point every request where to file bugs for community packages to the AUR comment fields. I see no good reason why we do that. We should have a dedicated bug tracking system with RSS feeds and maintainer assignment also for the community packages. Then everybody reading the feeds could help out fixing them. I expect a good improvement of the packaging quality. I don't know if it would be useful to also have it for the unsupported AUR packages. Maybe we should just start only with the supported community packages. What do TUs and other Devs think about it? And Roman? Andy
Am Mittwoch, 24. Oktober 2007 19:55:15 schrieb Andreas Radke:
What do TUs and other Devs think about it? And Roman?
+1 for [community] bug tracker and -1 for unsupported :-) I don't know any good reason why TUs shouldn't have access to the bug tracker. -- archlinux.de
On 10/24/07, Pierre Schmitz <pierre@archlinux.de> wrote:
Am Mittwoch, 24. Oktober 2007 19:55:15 schrieb Andreas Radke:
What do TUs and other Devs think about it? And Roman?
+1 for [community] bug tracker and -1 for unsupported :-)
I don't know any good reason why TUs shouldn't have access to the bug tracker.
Agreed. If no nay-sayers in the next few hours, I will set this up.
Aaron Griffin schrieb:
I don't know any good reason why TUs shouldn't have access to the bug tracker.
Agreed.
If no nay-sayers in the next few hours, I will set this up.
+1 from me as well. The TU group has done good work in the past, flyspray will help them do better work and coordinate requests and bugs better, track dependencies between bugs and so on.
Andreas Radke wrote:
You all know we don't have a special category for community packages in our bug tracker. But why? I haven't seen any request for it until now.
So far we point every request where to file bugs for community packages to the AUR comment fields. I see no good reason why we do that. We should have a dedicated bug tracking system with RSS feeds and maintainer assignment also for the community packages. Then everybody reading the feeds could help out fixing them. I expect a good improvement of the packaging quality.
I don't know if it would be useful to also have it for the unsupported AUR packages. Maybe we should just start only with the supported community packages.
What do TUs and other Devs think about it? And Roman?
+1. I agree we should just do this for [community] packages at least initially. - P
2007/10/24, Andreas Radke <a.radke@arcor.de>:
You all know we don't have a special category for community packages in our bug tracker. But why? I haven't seen any request for it until now.
So far we point every request where to file bugs for community packages to the AUR comment fields. I see no good reason why we do that. We should have a dedicated bug tracking system with RSS feeds and maintainer assignment also for the community packages. Then everybody reading the feeds could help out fixing them. I expect a good improvement of the packaging quality.
I don't know if it would be useful to also have it for the unsupported AUR packages. Maybe we should just start only with the supported community packages.
What do TUs and other Devs think about it? And Roman?
See this thread: http://archlinux.org/pipermail/arch-dev-public/2007-May/000698.html -- Roman Kyrylych (Роман Кирилич)
participants (6)
-
Aaron Griffin
-
Andreas Radke
-
Paul Mattal
-
Pierre Schmitz
-
Roman Kyrylych
-
Thomas Bächler