Re: Forward bugs upstream to myself?
In an attempt to save the world from disaster, Andy Mortimer wrote:
> Dear all,
>
> [ I suppose this is a `meta-policy' question, and as such should possibly go
> to debian-policy, but I'm not subscribed to that. ]
>
> The problem: I maintain a package (dpkg-mountable), for which I am also the
> `upstream' author. Over a year ago now, Dirk Eddelbuettel filed a bug against
> it (#7957), and although it's a real problem, to fix it would require a
> radical rewrite of most of the code. Which I don't really want to do.
>
> I could file it as wishlist, but it seems to make a lot more sense to mark it
> as forwarded (ie, waiting for the upstream author to get off his backside and
> do something with it), since that gives a more accurate idea of the status of
> the report. But it does seem a little cheeky, too ...
I like it, though!
D: How about #7957?
A: Ah, I forwarded it upstream.
D: What did upstream say?
A: Well, he's not very active at the moment. To be honest, I've
yet to hear back from him.
D: Yeah, these upstream maintainers, can be a real pest some time.
> What do people think?
Well, for one thing, there's nothing in the docs that is against it.
And, thinking about it, I think I'll start using that feature too,
with menu, etc. Yeah, I like it!
Wonder what your upstream author things about my .sig?
--
joost witteveen, joostje@debian.org
The upstream maintainer is allowed to do things different
than Debian, but only if he has good reasons to do so.
--
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: