tag 490265 - patch thanks On Wed, 01 Sep 2010, Atsuhito Kohda wrote: > On Thu, 26 Aug 2010 17:16:49 -0700, Don Armstrong wrote: > > I really think we should ditch the lynx-cur package, and just call > > it lynx; reopening and degrading the severity to indicate as such. > > Okay. > > > Secondly, this is not the way that you close bugs that you've > > forgotten to close. Send messages to -done with an explanation of > > why they should be closed. > > Yes,I got an email from another DD which claimed almost the same > thing as you did.
Yerp; see the Developers Reference ยง5.8.4: http://www.debian.org/doc/developers-reference/pkgs.html#upload-bugfix > In case of this bug, I closed the bug simply because I noticed a > sentence: "Anyway, feel free to close this bug report" in your > report but I might overlooked the sentence "if you feel that the > above has been weighed, and that you've contemplated the concerns > that I have." following the above. > > I guessed there were no need to explain why they were closed > because they were all trivial. Well, a single one line explanation to -done is generally sufficient. In my case (and in the case of other developers) it's less of a problem, because we can read between the lines... but users won't know why their bug was closed unless you tell them specifically. Just to reiterate my suggestion: Plan to keep lynx transition package in future? Yes: Rename lynx-cur to lynx, stop distributing lynx-cur No: Retitle bug; remove lynx transition package after squeeze. FWICT, there's no one who is planning on distributing a "stable release" of lynx (and furthermore, they cannot, as long as the lynx transition package exists), so one of the two above things should be done. Don Armstrong -- a friend will help you move a best friend will help you move bodies but if you have to move your best friend's body you're on your own -- a softer world #242 http://www.asofterworld.com/index.php?id=242 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
