Re: Bug Reporting system
James Troup wrote:
>
> Goswin Brederlow <goswin.brederlow@student.uni-tuebingen.de> writes:
>
> > > > My proposal is to add an architecture field to the maintainer
> > > > and having one maintainer for each architecture.
>
> [...]
>
> > For something like m68k, where there are not enough maintainers at
> > the moment, the mails would go the list. If someone there finds that
> > he knows the package and uses it frequently, he can then sign up as
> > maintainer for the architecture.
>
> We have ~6 active (pushing it) maintainers for m68k, other non-i386
> architectures have a similar number *or less*, just how many packages
> do you expect to have "architecture maintainers" for? I say again,
> it's not workable.
There was a list with maintainers of m68k stuff lately. Something of
20-30 packages. SO what? Even if we only have this 20-30 packages
maintained for m68k and all others unsuported, bugs reported would be
sorted to the maintainers or to the apropriate list. The i386 maintainer
wouldn't be bothered by some bugs of other architectures (like xpaste
m68k depending on X11R6 which is obsolete). How could I report a bug
like xpaste at the moment? By having (or not having) maintainers for
architectures the i386 maintainer wouldn't be bothered by a bug report
for m68k.
>
> > > Oh, yeah and it would also break completely if/when
> > > auto-compilation gets under way.
> >
> > Why would it break auto-compilation? I can't see a reason why. Pleas
> > explain a bit further.
>
> Read what I wrote. I said it would break *with* auto-compilation,
> since then there are no architecture maintainers any more.
>
> (Assuming of course auto-compilation ever takes of)
If it breaks maintainer fields for architectures it would also break the
maintainer field as it is now.
The maintainer information should just be left as it is by the
autocompilation. If it autocompiles for an unsuported architecture so
what? It can leave the filed empty or insert the right mailinglist
depending on the setup.
Autocompileing should on no account change the information about the
maintainer. No matter if it is one or many.
>
> --
> James
May the source be with you.
Mrvn
--
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: