Re: Bug Reporting system
Goswin Brederlow writes:
> I didn't say 20-30 maintainer, I said 20-30 Packages. Thats a big
> difference.
>
> > So, you want people to go to the hassle of adapting the bug tracking
> > system and dpkg-* to support architecture-specific maintainers for
> > 20-30 packages (your flawed estimate), which is what? 2% of the
> > Packages (real figure == .2%)? It's not worth it.
>
> May be it's not worth now, but there will be more maintainers and more
> bugs. Maybe having multiple maintainers isn't the right thing, but
> somehow bugreports should be send to the right list, i.e. debian-arch.
I believe the normal way is that the particular maintainer receives
the bugreport and thinks over it. If it is architecture specific
he looks for a particular person who works on tht architecture. If not
the bug should be forwarded to a more specific list.
At least this is true for me and my packages. I don't see a problem
in this procedure. It's very logical to me. Nevertheless it might
be a good idea to document this in the policy if it is not in already.
(but I can't provide that)
> I sugested having multiple maintainers for the archs, which might not be
> worth for 0.2%. Maybe adding an archi field to the bugreports is worth
> it then? Can we come to terms on that?
I don't see much sense in this.
> Maybe we could make a list of people supporting packages on different
> architectures. So newbies can look up whom to mail if they have problems
I believe it makes much more sense if the people who work on the
same packages but on different architectures would know each other
and talk about the problems. Again this sounds very logical to me.
Regards
Joey
--
/ Martin Schulze * joey@infodrom.north.de * 26129 Oldenburg /
/ No question is too silly to ask, /
/ but, of course, some are too silly to answer -- perl book /
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: